Forum Moderators: bakedjake
It's quite interesting - occasionally we get hit with a large unexpected volume of traffic - we have one application (not web related) which always needs to keep running, so I set it's NICE value to -1 and have apache set at 5.
Most of the lower priority processes I've now set at between 5 and 10.
It has made a noticeable difference.... which I didn't expect. The website actually appears faster - I guess that's from lowering the priority of the low-importance processes.
Any have some insights and experience with ideal settings for webservers?
TJ
Keep things in different partitions - so one full section of the hard drive doesn't take the server offline. I don't put the logs in the same partition as anything else. Actually, I put the logs on a seperate drive.
Non-essential services I only run when needed. For example webmin. I log in to the server and start the webmin daemon when I want to use it, then shut it down when I'm done.
Outside of specific software tweaks, those things I find have helped me trim what's happening on the server substantially. Though your nice idea is great, I'll have to look at it shortly. Is there a way to force a program to a specific nice level evertime it's started (I know how to change the priority of a running process, but can it be automated?)
Glad there's someone else around interested in chatting about these issues. Thanks for the tip about removing stuff you don't know about. There's a few processes I have running and haven't got a clue what they're doing. I'll do some digging and find out if I can safely remove them.
Is there a way to force a program to a specific nice level evertime it's started (I know how to change the priority of a running process, but can it be automated?)
Just prefix at the command line, eg:-
NICE -n 5 httpd
To run httpd with a reduced priority of 5.
TJ
Also any allow from/deny from rules should make use of numbers, not names. It's been a while, but I think that with resolution turned off names in ACLs won't work anyway.
Sean