Heya all,
I'm working on testing ZFS with NFS, and I could use some guidance - read
speeds are a bit less than I expected.
Over a gig-e line, we're seeing ~30 MB/s reads on average - doesn't seem to
matter if we're doing large numbers of small files or small numbers of large
files, the speed
cross-posting to nfs-discuss
On Oct 20, 2009, at 10:35 AM, Gary Gogick wrote:
Heya all,
I'm working on testing ZFS with NFS, and I could use some guidance -
read speeds are a bit less than I expected.
Over a gig-e line, we're seeing ~30 MB/s reads on average - doesn't
seem to matter if
Gary
Where you measuring the Linux NFS write performance? It's well know
that Linux can use NFS in a very "unsafe" mode and report the write
complete when it is not all the way to safe storage. This is often
reported as Solaris has slow NFS write performance. This link does not
mention NFS v4
But this is concerning reads not writes.
-Ross
On Oct 20, 2009, at 4:43 PM, Trevor Pretty trevor_pre...@eagle.co.nz
wrote:
Gary
Where you measuring the Linux NFS write performance? It's well know
that Linux can use NFS in a very unsafe mode and report the write
complete when it is
No it concerns the difference between reads and writes.
The write performance may be being over stated!
Ross Walker wrote:
But this is concerning reads not writes.
-Ross
On Oct 20, 2009, at 4:43 PM, Trevor Pretty trevor_pre...@eagle.co.nz
wrote:
On Tue, Oct 20, 2009 at 10:35 AM, Gary Gogick g...@workhabit.com wrote:
We're using NFS v4 via TCP, serving various Linux clients (the majority are
CentOS 5.3). Connectivity is presently provided by a single gigabit
ethernet link; entirely conventional configuration (no jumbo frames/etc).
On Oct 20, 2009, at 5:28 PM, Trevor Pretty trevor_pre...@eagle.co.nz
wrote:
No it concerns the difference between reads and writes.
The write performance may be being over stated!
The clients are Linux, the server is Solaris.
True the mounts on the Linux clients were async, but so are
Trevor/all,
We've been timing the copying of actual data (1GB of assorted files,
generally 1MB with numerous larger files thrown in) in an attempt to
simulate real world use. We've been copying different sets of data around
to try and avoid anything being cached anywhere.
I don't recall the
