All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwight@supercomputer.org
To: Ian Kent <raven@themaw.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: RE: Linux client on Solaris 7 NFS server
Date: Wed, 07 Jan 2004 10:17:29 -0800	[thread overview]
Message-ID: <200401071817.i07IHTC20135@supercomputer.org> (raw)
In-Reply-To: Message from Ian Kent <raven@themaw.net> of "Tue, 06 Jan 2004 12:42:17 +0800." <Pine.LNX.4.33.0401061229170.26529-100000@wombat.indigo.net.au>

Thanks for the suggestion, Ian. It was a good one, and I've carried it a
little farther.

First, this is all single threaded at the user level. It's a mixture of
reads and writes; akin to a large compile (actually link) of a bunch of
files, creating one big binary. Just using a local disk, we're looking at
about 3-4 secs. Over NFS, it's 30 seconds, except for the Linux client case.

Doing just reads (dd of the 2.4.23 kernel source .tgz, which is about 35 MB),
it takes about 3-4 seconds. That's UDP, with a dd blocksize to match the
NFS r/w size of 8k, on a 100 Mbs network. So this matches your results.
This is for a Linux client talking to either a Linux or a Solaris server.

However, doing a write, I see different results. In the Linux/Linux case,
again the result is again about 3-4 seconds. However, with a Linux-client/
Solaris-server, it takes about 12 seconds. This is a factor of 3-4.

I'm wondering if the mixture of reads and writes is what is driving the
degradation up to a factor of 6.

I'll give the pure Solaris/Solaris results a try. Anecdotally, I've heard
that there are also similar issues with HP-UX and AIX, though I haven't
tried it out myself.

Best Regards,

	-dwight-


Ian Kent wrote:

> I had some figures, but I've deleted them.
> 
> Basically I'm saying, with a 100Mb(it)/sec interface I get just over
> 8 MB(ytes)/sec whereas I can consistently get over 10MB(ytes)/sec on most
> Sparcs (Solaris). So the Sparcs are pushing their interfaces about fast as
> they can go but the Linux box is not. So there's still room for
> improvement.





-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-01-07 18:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 15:50 RE: Linux client on Solaris 7 NFS server Lever, Charles
2003-12-30 17:44 ` dwight
2003-12-31  1:55   ` Ian Kent
2004-01-05 17:31     ` dwight
2004-01-05 19:46       ` Wade Hampton
2004-01-05 22:34         ` Wade Hampton
2004-01-06  4:59         ` Ian Kent
2004-01-06  7:41         ` dwight
2004-01-06  4:42       ` Ian Kent
2004-01-07 18:17         ` dwight [this message]
2004-01-08  0:32           ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2003-12-30 17:58 Lever, Charles
2004-01-05 17:11 ` dwight
2004-01-06  4:57   ` Ian Kent
     [not found] <Charles.Lever@netapp.com>
2004-01-05 18:21 ` Lever, Charles
2004-01-06  7:38   ` dwight

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200401071817.i07IHTC20135@supercomputer.org \
    --to=dwight@supercomputer.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=raven@themaw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.