On Thursday August 17, [email protected] wrote:
> In article <[email protected]>,
> Andrzej Szymanski <[email protected]> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
