On Thu, 2007-08-02 at 18:56 +0800, Ang Chin Han wrote:
> On 7/25/07, Ditesh Kumar <[EMAIL PROTECTED]> wrote:
>
> > is a sysload of 70 even feasible? i had me headless boxen go up to 17 at
> > one point because of misconfigured pgsql indexes; it was completely
> > unresponsive. 70 seems dodgy.
>
> Heh. Just nearly happened today:
> web{redacted}:~ # uptime
> 4:51pm up 10 days 4:43, 4 users, load average: 67.60, 68.22, 61.98
this is on the same xeon 1 core boxen?
did some reading on what uptime really means. apparently, depending on
the system its on, it can mean different things. on linux boxen,
sleeping processed blocked on i/o count towards load average, which may
or may not be accurate depending on what you think load average should
mean. so apparently, a responsive boxen with load avg of 70 is quite
feasible in such scenarios :)
my boxen which was not responsive on load avg of 17 because it was cpu
bound as opposed to being i/o bound.
--
May your signals all trap Ditesh Kumar
May your references be bounded [EMAIL PROTECTED]
All memory aligned http://ditesh.gathani.org/blog
Floats to ints rounded http://www.openmalaysiablog.com
_______________________________________________
Slugnet mailing list
[email protected]
http://www.lugs.org.sg/mailman/listinfo/slugnet
