Russell Coker wrote:
On Thu, 6 Feb 2003 17:32, Alexander Lyamin wrote:I propose that you try reversing the datalogging patch for long enough to know whether it is our new code that is buggy.
vmstat doesn't work properly. CPU time is 99% system which suggests that one CPU is spending all it's time in kernel space (for both threads of a hyper-threaded CPU) or that both CPUs have each got one thread locked in kernel space.i think i wasnt clear enough.One problem that has started occuring is that periodically some of thewhen its slows down, please check with vmstat for IO or with your
machines will go really slow for a while. It's as if the CPU speed has
just dropped to 1% of it's regular speed. Then after 10 minutes or so
it will continue as normal.
so - first , if you "go-slow" on a disk activity, chances are good
that it caused by FS or VM or their misunderstandings.
If it is not our code, and it matters enough to justify the cost, we can remote login kernel analyze for you for an hourly fee. Probably the fee you charge them is good enough for us too.;-)
--
Hans
