Hi all, I upgraded to SuSE 8.2 Professional a couple of days ago. Well done SuSE! This is poetry in motion! I have one problem: Open Office is really slow. I mean, really really slow. Screen update seems to be the culprit. If I click on the "open" button, the frame of the dialog box appears, but it takes a good 20 or seconds before anything gets drawn in it. Similarly, in the register dialog box, I clicked on "never register" and it took a good half a minute before it made the selection and I could click on "ok." Typing also lags big time. I can type a medium length sentance before it starts appearing on screen. There's no unusual hard disc activity, and cpu usage stands still while this waiting is going on. I replaced the default 1.0.2 with 1.1beta from www.openoffice.org, result is the same. Could this be a java problem (I heard recently that OOO uses Java for its gui, is this true?) or a display problem? Hardware is a athlon 1.5ghz, 256mb ram and nVidia graphigs. nVidia driver is installed, eveything else works like a charm. Thanks Hans
On Wednesday 28 May 2003 14:56, H du Plooy wrote:
Hi all,
I upgraded to SuSE 8.2 Professional a couple of days ago. Well done SuSE! This is poetry in motion!
I have one problem: Open Office is really slow. I mean, really
Nope, it's ok here (I'm using 1.1 beta2)
Could this be a java problem (I heard recently that OOO uses Java for its gui, is this true?) or a display problem?
Don't think so, cause OO can be installed without Java. -- -- Verdi March --
H du Plooy said:
Hi all,
I upgraded to SuSE 8.2 Professional a couple of days ago. Well done SuSE! This is poetry in motion!
I have one problem: Open Office is really slow. I mean, really really slow. Screen update seems to be the culprit. If I click on the "open" button, the frame of the dialog box appears, but it takes a good 20 or seconds before anything gets drawn in it. Similarly, in the register dialog box, I clicked on "never register" and it took a good half a minute before it made the selection and I could click on "ok."
Typing also lags big time. I can type a medium length sentance before it starts appearing on screen. There's no unusual hard disc activity, and cpu usage stands still while this waiting is going on.
I replaced the default 1.0.2 with 1.1beta from www.openoffice.org, result is the same.
Could this be a java problem (I heard recently that OOO uses Java for its gui, is this true?) or a display problem?
Hardware is a athlon 1.5ghz, 256mb ram and nVidia graphigs. nVidia driver is installed, eveything else works like a charm.
Hi Hans, I've got the same problem with OpenOffice running slowly on My PC. This is made far worse if I run the setiathome client. -- David Bottrill david@bottrill.org
On Wednesday 28 May 2003 4:29 am, David Bottrill wrote:
Could this be a java problem (I heard recently that OOO uses Java for its gui, is this true?) or a display problem?
Hardware is a athlon 1.5ghz, 256mb ram and nVidia graphigs. nVidia driver is installed, eveything else works like a charm.
Hi Hans,
I've got the same problem with OpenOffice running slowly on My PC. This is made far worse if I run the setiathome client.
I've done 5 installs of 8.2 on machines I own, and only one of those had this 'slowness' problem, and in my opinion the entire machine was slow. When I clicked to bring up OO(I run SO 6.0), the frame of the window would appear for several minutes before it filled in, and then it would take several more minutes before the mouse would 'come alive' in the application. (it wouldn't respond) The machine was a sick puppy. I did two things in an attempt to make things better: 1) Changed SETI to a nice=19 2) Rebuilt the kernel to my liking. Not sure which of the above did the most but the machine is back to where it was with 8.0 and 8.2 runs very nicely now. AMD Athlon 800mhz - All SCSI machine. 768MB -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/28/03 09:43 + +----------------------------------------------------------------------------+ "The sooner you fall behind the more time you'll have to catch up."
On Wed, 2003-05-28 at 15:47, Bruce Marshall wrote:
I did two things in an attempt to make things better:
1) Changed SETI to a nice=19
OK, that definitely made a difference. Setting seti to nice=19 made it much less unusable, but still too slow. stopping seti altogether, that helped.
2) Rebuilt the kernel to my liking.
Doing that right now to see if it will further help. In both SuSE 8.0 and 8.1 I had seti running 24/7 with nice=1 and I had no visible effect on anything but Quake3 and Wolfenstein. Openoffice always worked very nicely. Thanks, will report back once I have the new kernel going Hans
On Wednesday 28 May 2003 15:04 pm, H du Plooy wrote:
On Wed, 2003-05-28 at 15:47, Bruce Marshall wrote:
I did two things in an attempt to make things better:
1) Changed SETI to a nice=19
OK, that definitely made a difference. Setting seti to nice=19 made it much less unusable, but still too slow. stopping seti altogether, that helped.
2) Rebuilt the kernel to my liking.
Doing that right now to see if it will further help. In both SuSE 8.0 and 8.1 I had seti running 24/7 with nice=1 and I had no visible effect on anything but Quake3 and Wolfenstein. Openoffice always worked very nicely.
Me too... That is, in 8.0 I was running SETI at nice=2 with no problems. And even more strange, I was running a 2.4.20 kernel (same as 8.2) at the time... so one would think it is not a kernel issue with 8.2.
Thanks, will report back once I have the new kernel going
Hans
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/28/03 16:44 + +----------------------------------------------------------------------------+ "Time is the best teacher; Unfortunately, it kills all its students!"
I've noticed that OOo doesn't like it if there are other processes using the CPU. Tried it on several machines, SuSE 7.2 and 8.1 as well as 8.2 with various versions of OOo. Openoffice works fine, but if you do something like compile a kernel, or do some heavy image processing, it becomes unusable as you describe. I'm currently running an Athlon XP1700+. Looks like there's some kind of locking in the GUI code that doesn't like heavy CPU activity... KDE and other Apps remain responsive. I'm trying the newest beta, and it seems to work a bit better, but still takes 10-15 seconds to respond to mouse clicks while compiling something else. Oh well. On Wednesday 28 May 2003 9:29 am, David Bottrill wrote:
H du Plooy said:
Hi all,
I upgraded to SuSE 8.2 Professional a couple of days ago. Well done SuSE! This is poetry in motion!
I have one problem: Open Office is really slow. I mean, really really slow. Screen update seems to be the culprit. If I click on the "open" button, the frame of the dialog box appears, but it takes a good 20 or seconds before anything gets drawn in it. Similarly, in the register dialog box, I clicked on "never register" and it took a good half a minute before it made the selection and I could click on "ok."
Typing also lags big time. I can type a medium length sentance before it starts appearing on screen. There's no unusual hard disc activity, and cpu usage stands still while this waiting is going on.
I replaced the default 1.0.2 with 1.1beta from www.openoffice.org, result is the same.
Could this be a java problem (I heard recently that OOO uses Java for its gui, is this true?) or a display problem?
Hardware is a athlon 1.5ghz, 256mb ram and nVidia graphigs. nVidia driver is installed, eveything else works like a charm.
Hi Hans,
I've got the same problem with OpenOffice running slowly on My PC. This is made far worse if I run the setiathome client.
-- David Bottrill
david@bottrill.org
On Wed, 2003-05-28 at 11:09, Jason wrote:
I've noticed that OOo doesn't like it if there are other processes using the CPU.
Not true. It all depends on how busy the CPU is with other processes. Each process has to wait for its slice of the cpu time.
Typing also lags big time. I can type a medium length sentance before it starts appearing on screen. There's no unusual hard disc activity, and cpu usage stands still while this waiting is going on.
Again this also depends on busy the hard drive is, every process accessing the hard drive has to wait its turn in the queue. If you run a process the is CPU and IO intensive it will slow down every other process. OO is very PCU and IO intensive when it starts. One of the reasons i use 10k rpm drives and dual cpus. What a difference. Ken
On Wednesday 28 May 2003 5:11 pm, Ken Schneider wrote:
On Wed, 2003-05-28 at 11:09, Jason wrote:
I've noticed that OOo doesn't like it if there are other processes using the CPU.
Not true. It all depends on how busy the CPU is with other processes. Each process has to wait for its slice of the cpu time.
I realise this. But why is it only OOo that has serious problems when the system is loaded? Other apps respond fine, I can use Kword while compiling stuff. I can use Gimp fine. But OOo is unusable. I think my system (Athlon 1700, 768Mb, 7200rpm drives) has enough power for running the GUI, an office package and doing other stuff in the background.
Typing also lags big time. I can type a medium length sentance before it starts appearing on screen. There's no unusual hard disc activity, and cpu usage stands still while this waiting is going on.
Again this also depends on busy the hard drive is, every process accessing the hard drive has to wait its turn in the queue.
This doesn't explain why KDE, GTK and other X apps seem to work fine.... I can click from an unresponsive OOo window, into Kmail and start typing straight away.
If you run a process the is CPU and IO intensive it will slow down every other process. OO is very PCU and IO intensive when it starts.
But Openoffice _should_ work fine once it's loaded? On my system it doesn't if there are processor intensive things running as well.
One of the reasons i use 10k rpm drives and dual cpus. What a difference.
Maybe I'll have OOo running on a low power box accessed remotely through X. <grin> I'm not really complaining. I like and use OOo a lot -- it's just this one issue about it I find puzzling. I just don't use it if my system is using loads of CPU. I suspect it's something to do with OOo's internal architecture, that doesn't play well when a system is loaded. Jason
On Wed, 2003-05-28 at 23:51, Jason wrote:
Not true. It all depends on how busy the CPU is with other processes. Each process has to wait for its slice of the cpu time.
I realise this. But why is it only OOo that has serious problems when the system is loaded? Other apps respond fine, I can use Kword while compiling stuff. I can use Gimp fine. But OOo is unusable. I think my system (Athlon 1700, 768Mb, 7200rpm drives) has enough power for running the GUI, an office package and doing other stuff in the background.
Same here, I'm typing this in Evoluting while compiling my kernel and waiting for OOo to become useable. It's just Openoffice.
I'm not really complaining. I like and use OOo a lot -- it's just this one issue about it I find puzzling. I just don't use it if my system is using loads of CPU. I suspect it's something to do with OOo's internal architecture, that doesn't play well when a system is loaded.
My suspicion is that it's not OOo fault directly, rather something else (maybe in the kernel) that causes this. I installed OOo 1.1b from the same package in 8.1, and it didn't care if seti was running or not. Hans
participants (6)
-
Bruce Marshall -
David Bottrill -
H du Plooy -
Jason -
Ken Schneider -
Verdi March