On Thu, 27 Oct 2011 12:27:30 +0900, Malvern Star <malv_star@hotmail.com> wrote:
Has anybody else noticed a huge drop in desktop responsiveness under 12.1RC1 as opposed to Beta1? When I finally managed to install 12.1 Beta 1 (had to use text mode to install due to an X11 segfault during the second phase), the system was quick and responsive; incredibly responsive in fact - I was impressed. Now in RC1, using the KDE desktop feels like wading through sand. I'm not sure what's causing it, but the graphical effects are extremely choppy (Radeon HD 5670 in my test machine), with what can only be described as a "low framerate" during actions such as maximising and minimising windows.
I noticed some problems with responsiveness on rc1.
But to me it didn't seem gfx related. It seemed like disk issues - either disk sleep or just a lot of I/O making the system "freeze" for ½-1 second at very frequent intervals. Mostly seemed to happen after a few seconds of idleness.
I haven't quite been able to pinpoint what is actually happening though. It's a pretty default 12.1rc1 with strigi disabled and akonadi running - but with zero data in it.
What does iotop say?
iotop was initially (shortly after login) constantly showing a value of around 3.5 to 3.9 M/s for "Total DISK WRITE". This ended shortly afterwards and it showed 0.00 B/s for both read and write while I dragged around the various windows, however responsiveness remained very low.
top however shows Xorg using up to 100% CPU when I drag windows around. Is that normal? I suppose I can try comparing it to the Beta... -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Hello, I get this unresponsiveness too. The indicator I get is when the monitor program [gkrellm] shows a steep rise of a line in the the procs/users window. My desktop freezes completely. I have the seconds turned on in the the clock and sometimes that even stops updating too. I will attach an example gkrellm snapshot when the system is stalling. The only thing I can do is a system restart. Glenn