As mentioned before, IO could give such strange results. I suggest
launching
dstat with logging to a file, and analyzing the file afterwards.
Thanks, much appreciated!
This has yielded some interesting data, which I'll attempt to include
a few seconds before and after one of these events
On Thu, 2007-12-06 at 16:48 +0100, Tomasz 'Zen' Napierala wrote:
> Wednesday 05 December 2007 15:39:41 J. Potter napisał(a):
> > Hi List,
> >
> > I'm stumped by this:
> >
> > load average: 10.65, 594.71, 526.58
> >
> > We're monitoring load every ~3 minutes. It'll be fine (i.e. something
> > li
Wednesday 05 December 2007 15:39:41 J. Potter napisał(a):
> Hi List,
>
> I'm stumped by this:
>
> load average: 10.65, 594.71, 526.58
>
> We're monitoring load every ~3 minutes. It'll be fine (i.e. something
> like load average: 2.14, 1.27, 1.03), and then in a single sample,
> jump to someth
IO load takes IO wait into it's calculation, so it may be a writer process
hammering the disks which are under powered for the IO load.
Run an iostat under these situations to find the disks causing the high waits.
-Ross
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
T
4 matches
Mail list logo
