Process Manager Priority Values
The documents for Process Manager say this about the Priority value:
Priority A number between -20 and 20 that describes how much time the system uses to work on the process. -20 is the least CPU intensive, while 20 is the most CPU intensive.
Is this correct? When my Perl script sets its priority to 19, the Process Manager shows 19 in the Priority column. But if, according to the docs, I want to make my script low-priority, I should set my script to -19. If I do that, it shows 0 in the Priority column in Process Manager. In fact, if I set my script to *any* negative priority value, it shows up in Process Manager as 0 priority.
From a discussion about this on StackOverflow, I was told that Process Manager won't let me set my script's priority to a negative number because that would actually be *raising* it's priority, which the script doesn't have permission to do, but it can lower itself, so setting a positive value like 19 works, and Process Manager shows that it has indeed set its priority to 19.
It was suggested to me that the cPanel docs are reversed, so I wanted to ask if this is the case or why I'm seeing what I'm seeing with Process Manager and its reported priority values based on my script settings.
Thanks for any light you can shed on this...
-
Hello @swbrains, It looks like this is a flaw in our Documentation. I've opened internal case DOC-10761 with our Documentation Team to update this document to reflect that lower priority values correspond to more CPU usage. Thank you. 0 -
Thanks for clarifying! 0 -
Hello @swbrains, To follow-up, the document is now updated to better describe the Priority value: Process Manager - Version 70 Documentation - cPanel Documentation Thanks! 0 -
Thanks! 0
Please sign in to leave a comment.
Comments
4 comments