Messages in this thread | | | From | Neil Brown <> | Date | Mon, 21 Aug 2006 11:31:20 +1000 | Subject | Re: Strange write starvation on 2.6.17 (and other) kernels |
| |
On Thursday August 17, miquels@cistron.nl wrote: > In article <44E0A69C.5030103@agh.edu.pl>, > Andrzej Szymanski <szymans@agh.edu.pl> 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.
Can you report the contents of /proc/meminfo before, during, and after the long pause? I'm particularly interested in MemTotal, Dirty, and Writeback, but the others are of interest too.
Thanks, NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |