CPU usage 11.1 KDE 4.1

Hey all.
Have a question/issue regarding CPU usage under the titled install.
I get a constant 7-8 % usage at idle. Running TOP shows X server as the culprit (I have uninstalled Beagle and AppArmour) Usage is shown via gkrellm process stack. Is this normal? I suspect it is the new K desktop. Which is fine by me. What are other experiencing?
My hardware
CPU: AMD Athlon X2 6000 @ 3.1 GHz
MOBO: Asus M2N68
RAM: KVR800 4 x 1GB
GPU: Nvidia (ASUS EN8400GS) 8400GS
2 x HDD
1 x Optical

I ask because the same hardware was reporting 0-3% under 11.0 at idle. Please let me confirm this is NOT A *****! 11.1 is the best polished release I have installed. I am just curious as to what others are experiencing.

Yeah, that should be around 0-3%. Are you using some additional plasmoids?
Example with netmeter plasmoid your plasma desktop CPU usage is around 54-60% - of course it doesn’t uses 60% of your CPU. :slight_smile:

Thanks for the quick reply Ram (merry christmas to you and your family). Have changed the theme to Oxygen and that is about it.
Apache and FTP services are not giving me any activity at all. The machine is a DHCP Client (not server). No LDAP or Mail. The 8400 is %100 supported and the MOBO is also. Got me scratching my head!

Maybe gkrellm causes your X usage (it has some graphs, indicators, etc.). Close it and check your proc. usages (hit Ctrl+Esc).

ps.: yay! merry Christmas to you!

Nice option Ram. No joy. Give me a few days. I will post back with sonme more info. I should just reinstall. But setting up the LAMP server gives me the poo’s. It is seemingly different each time…grrrrrrrrrrr!

Hi,

I’ve got the same problem - after installing SUSE 11.1 with KDE 4 my CPU usage jumped to ca 15% at idle time. I then reinstalled SUSE 11.1 with KDE 3.5 (3.5.10). It did help a little bit as CPU usage went down to being constantly 7-8%, but it’s still worse than it used to be with SUSE 10.3 (1-2% at idle). top shows that X is to blame which eats up most of the CPU.
BTW, I also noticed that the KDE 3.5 which comes with SUSE 11.1 contains some KDE 4 elements (which wasn’t the case with the KDE 3.5 in SUSE 10.3, AFAIK). Probably, that’s the reason why the CPU usage has climbed higher.

As for the hardware, I’ve got IBM/Lenovo T60 (CPU Intel T2400), RAM 1 GB, graphics card is Intel’s built-in.

Any ideas how to get the CPU usage down?

I have noticed a similar issue on my system. (OS 11.1 64-bit, 3Ghz Pentium D, 2Gb Ram, Intel 946GZ video). CPU use floats between 8-12% with nothing running but KDE 4 using CTRL+ESC. The only thing on the desktop is the Suse button menu.

I already removed the Beagle in Yast, and shut down App armor. Checked out system services to make sure nothing is running that shouldn’t be for a work station. I’m out of ideas, but would still like to see the cpu load drop somewhat.

I’m getting 3-4% and that is with FF and sysmonitor running.

htop indicates me that sometimes, X is taking between 10 and 50 % of cpu with kde4.1 .

The title of this note brought me to here. I too experienced some CPU usage problems. Over-Usage. My new Dual Core PC has a fan on it that will really rev up when the processor kicks in to heavy usage. I was getting to many of those in this latest version of openSuSE 11.1 :O. To make the story short, the fix is:

YaST2->Software Management->Filter:Repositories->All in this list->Update if newer version is available

After setting the above conditions and then clicking on Accept it will seem like it is re-installing everything. After the above I no longer got all those over-drive conditions and my CPU usage at idle in top dropped from 7-8% down to 1-3%.rotfl!

Thanks for that tip, chucktr. I’m going to check that out.

I went back through my system settings again to make sure I didn’t have anything running that I didn’t need. (Servers, Services, etc.

Found that Apparmor was still running, so turned it off. I installed a couple of apps that I was missing and some updates that came up in Yast, then rebooted. Problem solved, although I have no idea what fixed it. :open_mouth:

I now have a 3-4% cpu load with firefox, vuze, and top running in a terminal! Don’t know what fixed the problem exactly, but it definitely seems to be related to the updated software.

Cheers.

I solved the mystery of ‘7-8% CPU usage’ - it was ksysguard itself that was taking it so much. When I closed it and watched everything through ‘top’, CPU usage went down to 1%.
However, the problem still remains - the applications which used to take less CPU in SUSE 10.3 are using it much more in 11.1. Some that used to take 5% are taking now around 30% and so on. It looks like the cost of some operations in X has gone up.

I’m back with bad news.:disapointed: It seems that Xorg will kick the CPU into a 92-97% usage while the machine is sitting idle. It takes about 15 minutes for this to happen and to stop it, you just hit the shift key or move the mouse. It is a bug and has been reported by many.(Bug #461335) I do believe that the Developers are working on it. Till then we don’t want to leave our PC’s on for long periods of time with no activity. Would be a shame to burn up a lot of neat machines … doing nothing.:open_mouth:

Strangely enough I have fixed my problem. I spent a fair amount of time poking around the system from a software point and didnt manage to have any impact on my constant 6-9% idle usage.
I had a spare pci-e 7950GTX in the cupboard. So as a last roll of the dice I pulled the 8400GS out and popped the 7950 in. Its a bit of a waste in a machine that is essentially a server and plays nothing more than Supertux when my daughter gets bored.
I booted the system with an init 3 argumanet. Ran Yast2 from a # and accepted the settings as they appeared to be correct. I dropped back to # and called sax2. Again everything appeared to be detected correctly (as it did with the 8400 I might add) at # init 5> logged in as my self and BAM! The dirt was gone! CPU is 1-3% at idle constantly. Even with the screen saver running I only hit 4%.

Go figure? I know others are having similar issues with CPU usage. It would seem there is more than one likely culprit. In my case it was the GPU. Few people have spare cards sitting around to try this out. But thats my story and perhaps it may help others.