|
reader would shoot back immediately with stuff like CPU, memory and
network load. Let's treat them one by one:
Status: O
X-Status:
X-Keywords:
X-UID: 11
(All of the following is assuming that the realservers are runnig linux.
At least I'm going to deal with only such cases for now)
1) CPU: How good is polling /proc/loadavg? My problem with that is the
load introduced by the measurement itself if polling is done too often.
Besides, how good is the info in loadavg? Doesn't it just
measure the number of processes in the queue every few milliseconds or
so to calculate the load. One could argue (and many people do argue)
that this is not a good metric of CPU load. Any ideas ??
2) Memory: We could just do what free command does (which is
just reading /proc/meminfo). Is that good enough. Anybody see any
pitfalls in that approach? Of course, polling /proc too often is again
a problem here. Besides that ??
3) Network: This is the hardest one. What would be a good metric of
network load... number of alive TCP connections?? Is that good
enough... I'm not deeply familiar with the kernel networking code. Could
somebody who is more familiar would throw some more light on this....
I'm eagerly looking forward to a good discussion on these topics...
Please feel free to send me a direct email if you don't want to send one
to the list.
Chetan Ahuja
Masters student in Comp. Sci.
Mich. State Univ.
|
