-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/05/08 08:36 AM, Ugo Bellavance wrote: > Terry a écrit : >> I am sitting here racking my brain on this one. Is dividing the load >> average by the number of CPUs a smart thing to do? the 'uptime' >> command on a box does not do this. So, if I have an 8 core box >> sitting with a load average of 8, its the same as a single core box >> sitting with a load average of 1? I'll see the same type of server >> response? Thoughts? > > It depends. What are you running, cpu-intensive processes? Multi or > single-threaded? I/O intensive processes? If you are running mostly I/O > intensive process, don't forget that your I/O subsystem (hard drives) is > shared among all processes, no matter how many CPUs you have.
I fully agree with that; however I don't think looking at the load average is always the best way to determine when i/o becomes a bottleneck. It greatly depends on the application type. Is there a fixed number of "readers" or will in increase with system load? If it's fixed, chances are that load-average will rapidly become equal to that number of readers, and any load increase will only decrease the response time for clients. Also will application using assync i/o even make the load-average raise? (I don't think so...) Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIJM/m6dZ+Kt5BchYRAuMYAKC0UhfG3Cj7vzvbq8sIabEd7Jv9aACeLayt m+H6FxMoPvdEmQZm0XVjxPE= =+Zah -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
