The Ubuntu community has contributed 11092 ideas, 50731 comments, 1079046 votes
Idea
#5806: Applications that stop 'responding' should get less CPU
|
| |
377
|
|
|
Written by bescritt the 27 Mar 08 at 00:30.
Category: System.
Related to:
Nothing/Others.
Status: New
|
|
|
Description
This can be implemented by doing a renice on any CPU-hogging processes that don't catch SIGXCPU.
This would be easy to implement, would improve responsiveness, and wouldn't break anything.
Similar functionality has been available on W*****s for some time with the ForumWare program "ProcessTamer".
This suggestion is an intentional duplicate, but with a less technical title.
Tags:
(none)
Attachments
No attachments.
Duplicates
Comments
|
Auzy wrote on the 27 Mar 08 at 01:07
| |
+1, as I said before, its innovation
|
|
unimatrix wrote on the 27 Mar 08 at 12:47
|
There's a reason this is not implemented. And the reason is that it's NOT easy at all.
How do you detect when an application isn't responding? As you wrote it hoggs the CPU.
Now, try running glxgears and see what happens. If you don't have v-sync on the CPU usage goes up to 100%. But hey, It's responding quite nicely.
So unless there's a reasonable way to do this, I'm against it.
|
|
TBH wrote on the 27 Mar 08 at 13:56
| |
Compile kernel by yourself , use preedemtion model
|
|
spyyder wrote on the 27 Mar 08 at 17:55
| |
I would argue that the opposite could be true. Give more cpu power so a program can resume response. Not all program halts are due to non-response.
|
|
mkbosmans wrote on the 27 Mar 08 at 18:36
|
This has nothing to do with the halting problem, because it doesn't matter whether te program will stop executing in a finite amount of time. The only thing that is important is that the program responds to signals within a given amount of time.
It is perfectly possible to have a program consume 100% CPU, but still be responsive and in fact this is the desired behaviour. This suggestion applies to programs that aren't so well written and stop responding.
|
|
mridkash wrote on the 30 Mar 08 at 18:17
| |
I think it already detects when the application is not responding and offers to stop it or continue. While sometimes I've seen this thing misfiring. Searching in Synaptic for ex. on my Laptop (slow hdd) the window goes into non responding state for some time. Happens with firefox sometimes, when java or something loads. There is lot of chance of misfiring and killing the wrong person... I mean process.
|
|
6205 wrote on the 2 Apr 08 at 05:07
| |
AGREE AGREE AGREE....damn FF2...it kills my CPU
|
Post your comment
|
|
