Show Posts
1
ProcessTamer / Optimization Suggestion: Adjusted Priority_Range
« on: April 17, 2007, 07:01 PM »
Hi,
I think i have an optimization idea, it could be called Adjusted priority_range per process:
The current version of PT tames all the process within the same global priority_range namely:
[ idle <-> below_normal <-> normal <-> above_normal <-> high ]
Which is good enough for the most common processes.
But there are some significant processes that will not work optimally within this global priority_range. every
one of this processes needs a unique Adjusted range to work better.
For example: processes that running multimedia content like Winamp.exe, Wmp.exe and even Iexplore.exe (when
running embedded multimedia content like You-Tube).
Certainly those processes which are CPU voracious occasionally deserved to be tamed and PT should lower their
priority.
But lowering them too much to the idle priority will cause interruptions and clippings in the multimedia content (!).
So they need a unique Adjusted range in which the lowest level is below_normal and not idle.
The same principle fits for the boost function: boosting those processes for instance to the high priority will
freeze the PC. So in the same way some processes need a unique Adjusted range in which the highest level is
above_normal or even normal and not high.
In sum if we take the Winamp.exe process for example it's Priority_Range should be:
[ below_normal <-> normal <-> above_normal ]
Another example- the Priority_Range of my AntiVirus scanner should be:
[ idle <-> below_normal <-> normal ]
otherwise boosting it too high will freeze the PC ( I'm using Kaspersky ;-) )
Obviously PT should use by default the global priority_range to every new process.
The user may change it individually to optimize some process.
Addition Edit (summing Hasi suggestions as specified in replies 4, 6) :
1] A functionality to define the initial ("basic") priority of a process - the process's starting priority. (like the functionality of the PRIO application: http://www.prnwatch.com/prio.html ).
2] A functionality to tune specific triggers (low & high) for each process. (the current global triggers will apply to processes with no specific rule).
3] A functionality to tune also the "default global priority_range" (which applies by default to all other processes which have no specific Priority_Range, as i mentioned above in my initial suggestion ).
If the idea is not clear enough , I would be glad to suggest additional explanations.
Thanks
.
I think i have an optimization idea, it could be called Adjusted priority_range per process:
The current version of PT tames all the process within the same global priority_range namely:
[ idle <-> below_normal <-> normal <-> above_normal <-> high ]
Which is good enough for the most common processes.
But there are some significant processes that will not work optimally within this global priority_range. every
one of this processes needs a unique Adjusted range to work better.
For example: processes that running multimedia content like Winamp.exe, Wmp.exe and even Iexplore.exe (when
running embedded multimedia content like You-Tube).
Certainly those processes which are CPU voracious occasionally deserved to be tamed and PT should lower their
priority.
But lowering them too much to the idle priority will cause interruptions and clippings in the multimedia content (!).
So they need a unique Adjusted range in which the lowest level is below_normal and not idle.
The same principle fits for the boost function: boosting those processes for instance to the high priority will
freeze the PC. So in the same way some processes need a unique Adjusted range in which the highest level is
above_normal or even normal and not high.
In sum if we take the Winamp.exe process for example it's Priority_Range should be:
[ below_normal <-> normal <-> above_normal ]
Another example- the Priority_Range of my AntiVirus scanner should be:
[ idle <-> below_normal <-> normal ]
otherwise boosting it too high will freeze the PC ( I'm using Kaspersky ;-) )
Obviously PT should use by default the global priority_range to every new process.
The user may change it individually to optimize some process.
Addition Edit (summing Hasi suggestions as specified in replies 4, 6) :
1] A functionality to define the initial ("basic") priority of a process - the process's starting priority. (like the functionality of the PRIO application: http://www.prnwatch.com/prio.html ).
2] A functionality to tune specific triggers (low & high) for each process. (the current global triggers will apply to processes with no specific rule).
3] A functionality to tune also the "default global priority_range" (which applies by default to all other processes which have no specific Priority_Range, as i mentioned above in my initial suggestion ).
If the idea is not clear enough , I would be glad to suggest additional explanations.
Thanks
.