Re: Strange write starvation on 2.6.17 (and other) kernels
From: Miquel van Smoorenburg
Date: Thu Aug 17 2006 - 04:34:34 EST
In article <44E0A69C.5030103@xxxxxxxxxx>,
Andrzej Szymanski <szymans@xxxxxxxxxx> wrote:
>I've encountered a strange problem - if an application is sequentially
>writing a large file on a busy machine, a single write() of 64KB may
>take even 30 seconds. But if I do fsync() after each write() the maximum
>time of write()+fsync() is about 0.5 second (the overall performance is,
>of course, degraded).
I'm seeing something similar.
I upgraded one of our newsrouters from 126.96.36.199 to 188.8.131.52 because
I needed ethernet bonding with vlan support.
It performs quite a bit worse now that before. The nightly report
that the INN software writes, tells me that the average write()
time (of the single threaded innd process to news storage) went
up from min/avg/max 0.942/1.716/2.337 ms to min/avg/max
The innd process writes to a simple filesystem I wrote myself that
shows a blockdevice as a single large file. It's a bit more efficient
than using the blockdevice directly.
So I don't see large write delays, but the average write() time
has gone up significantly (bad in my case, since it starves the
Since I've also had several unexplained hangs I'm going back
to 2.6.14.x for now, since this machine is too important .. as
soon as I've got some more redundancy I'll experiment some more.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/