misteride
02-12-07, 05:46 PM
I thought I would try the "nice" directive in our miva.conf (in this case, it is for v3.97), to see if i could easily elbow Miva ahead of some other processes such as MailScanner.
When I set "nice=10", and then run top, I can see that the setting has been acknowledged, and miva has a NI value of 10.
However, when I set "nice=-10", that NI value stays at 0, suggesting that it might be possible only to reduce the priority level of miva, but not increase it. This might be a safeguard for operating in a virtual-hosting environment, where we wouldnt want to get too piggy. But we're on a dedicated server, and are our only site, so we should be able to be as piggy as we like.
The Miva documentation even with its typographical error, suggests strongly that the full range of +20 to -20 is available.
And for anyone else interested in trying this out, the expression is "nice=10", not "nice=+10" which will bring your store to a screeching halt!
Anyone have any ideas here?
( Running Apache on Linux. Dedicated server. Suexec running because we have Ensim running.)
Thanks
Roger Ide
When I set "nice=10", and then run top, I can see that the setting has been acknowledged, and miva has a NI value of 10.
However, when I set "nice=-10", that NI value stays at 0, suggesting that it might be possible only to reduce the priority level of miva, but not increase it. This might be a safeguard for operating in a virtual-hosting environment, where we wouldnt want to get too piggy. But we're on a dedicated server, and are our only site, so we should be able to be as piggy as we like.
The Miva documentation even with its typographical error, suggests strongly that the full range of +20 to -20 is available.
And for anyone else interested in trying this out, the expression is "nice=10", not "nice=+10" which will bring your store to a screeching halt!
Anyone have any ideas here?
( Running Apache on Linux. Dedicated server. Suexec running because we have Ensim running.)
Thanks
Roger Ide