argh. It's not hard to understand. It's the average of how many processes are using the CPU *at once*, over a given time period. I truly don't give a rat's ass how you *guess* how your servers are performing. But giving load average such a high priority in your decision clearly makes it a guess. Doowutchyalike. What makes you think there are 9 million different man pages for a given app? heh. /me shakes head
On 6/25/05, Ian mu <[EMAIL PROTECTED]> wrote: > I don't think it means 100% at all. No idea where you get that from. > Its just your explanation doesn't make sense. How can it be how many > processes have used the cpu in the last minute? Are you saying when > load is 0.5 half a process has used the cpu in the last 5 mins? > Basically you're not making sense is the problem. > > Load is the amount of processes on average "waiting". Thats VERY > different. I.e if your load is 1, it means on average there is always > 1 process waiting to grab some cpu time. If load is 2, there are 2 > processes waiting on average to keep it pretty simplified. > > Load doesn't directly relate to cpu "usage", no one has said that > iirc. I would say people need to watch both. A load > 2 on a single > cpu will start to give bad performance on games even if cpu usage is > 30% (you can get this on certain maps/games for example). Load for me > is "generally" a better indicator than cpu usage as it gives a better > viewpoint of responsiveness of servers (imo). But I wouldn't let a > game machine go over load 2 or load 70% as a rule of thumb for me. > > Not sure what man page you're looking at btw. -- Clayton Macleod _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
