1 |
daid kahl wrote: |
2 |
>> 2009/11/25 Helmut Jarausch <jarausch@××××××××××××××××.de>: |
3 |
>>> Hi, |
4 |
>>> |
5 |
>>> on one of several machines and only occasionally |
6 |
>>> my X-server (/usr/bin/X) takes nearly 100% CPU. |
7 |
>>> I have killed some applications but this didn't help |
8 |
>>> unless I killed X itself and restarted it. |
9 |
>>> |
10 |
>>> Is there any way to find out what is hogging my X server? |
11 |
>>> |
12 |
> |
13 |
> Another thing worth note is what version of the kernel you are running |
14 |
> versus how updated X is. I noticed when I migrated to libxcb under a |
15 |
> 2.6.27 kernel that X starts running much more slowly for strange cases |
16 |
> (like when audio is running, for example, X hogs the processor). |
17 |
> |
18 |
> I don't have a lot of insight as to how to determine which program |
19 |
> makes X run hot, except for running very few things in X and starting |
20 |
> a program and keeping an eye on something like top. |
21 |
> |
22 |
> But, in any case, another solution may be to keep the kernel updated |
23 |
> if you are running the latest X software. |
24 |
> |
25 |
> ~daid |
26 |
> |
27 |
What is the process that causes the trouble? After the latest update I |
28 |
also found my KDE to be under high cpu load. The offending process was |
29 |
kwin. After some googling I found that switching off Vsync could help |
30 |
me. This option is in System Setting -> Desktop -> Advanced Options. |
31 |
That helped in my case. |
32 |
Hope, that can help. |