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