On 06/08/2010 17:29, Matthew Hodgson wrote:
Matthew Hodgson wrote:
Is there any way to tune the linux NFSv3 client to prefer to write
data straight to an async-mounted server, rather than having large
writes to a file stack up in the local pagecache before being synced
on close()?
In other news, whilst saturating the ~10Mb/s pipe during the big write
to the server, I'm seeing huge delays of >10 seconds on trying to do
trivial operations such as ls'ing small directories. Is this normal, or
is there some kind of tunable scheduling on the client to avoid a single
big transfer wedging the machine?
Hm, on reading the archives, it seems that this is a fairly common
complaint when dealing with large sequential workloads - a sideeffect of
the write pagecache not writing out smoothly.
What is the status of the '[PATCH] improve the performance of large
sequential write NFS workloads' patchset at
http://www.spinics.net/lists/linux-nfs/msg11131.html? It seems that it,
and its predecessors, are intended to fix precisely this issue. It
doesn't seem to have landed in mainline, though, and I can't find any
mention of it since http://lwn.net/Articles/373868/.
thanks,
Matthew
--
Matthew Hodgson
Development Program Manager
OpenMarket | www.openmarket.com/europe
matthew.hodgson@xxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
