From: Eric Whiting <ewhiting@amis.com>
To: Fabrizio Nesti <nesti@medialab.sissa.it>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: 2.4.20 TCP server + solaris client performance
Date: Wed, 19 Feb 2003 10:56:45 -0700 [thread overview]
Message-ID: <3E53C55D.1FCF2982@amis.com> (raw)
In-Reply-To: Pine.GSO.4.40.0302191211380.29315-100000@bodoni
Fabrizio,
2.4.20 NFS server testing -- I had been using bonnie numbers to judge
performance. Users and applications had not reported problems. I had not tried
your tar -xf cvs.tar test.
I just tried your tar -xf cvs-1.11.5.tar test and I see numbers like yours
(except I don't see super fast solaris NFS numbers)
Client Server Time
-------------------------------------
solaris7 2.4.20 27.3
solaris7 solaris9 26.9
solaris9 solaris7 25.3
2.4.18 2.4.20 7.0 (defaults to async mounts right?)
2.4.20 2.4.18 15.1
linux local (no NFS) 1.2 (including sync)
I think what we are seeing is partially the overhead in the creation of 500+
small files...
I'm not sure there is a major NFS UDP/TCP problem here -- but the differences
between your sun server and your linux server are interesting. Perhaps there is
a sync option that is making those numbers look different?
My solaris boxes are UFS. (are you runing veritas?)
My linux boxes are reiserfs.
The above numbers are on 100M network.
Please try bonnie tests for additional insights. Different tests show different
bottlenecks and advantages. Bonnie testing usually shows other areas where linux
NFS can do better than solaris NFS.
eric
Fabrizio Nesti wrote:
> So, if it is not UDP/TCP or r/wsize the cause, what can it be?
> Even more, after the email from
>
> > Eric Whiting <ewhiting@amis.com>
> > ...
> > We are getting good NFS numbers with 2.4.20 UDP NFS servers against solaris
> > [89] clients.
>
> So Eric, can you please show your configuration?
>
> Also it is strange that a standard out-of-the-box RH8.0 on that big server
> does perform so bad. Knowing this in advance, we wouldn't have chosen
> linux for serving... :(
>
> Ok,
> thanks and ciao,
> Fabrizio
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-19 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:36 2.4.20 TCP server + solaris client performance Fabrizio Nesti
2003-02-18 2:36 ` Alan Powell
2003-02-18 10:43 ` Fabrizio Nesti
2003-02-18 15:29 ` Eric Whiting
2003-02-18 15:47 ` Fabrizio Nesti
2003-02-19 4:39 ` Neil Brown
2003-02-19 11:30 ` Fabrizio Nesti
2003-02-19 14:07 ` Ion Badulescu
2003-02-19 15:27 ` Fabrizio Nesti
2003-02-19 15:47 ` Ion Badulescu
2003-02-19 16:54 ` Fabrizio Nesti
2003-02-19 17:56 ` Eric Whiting [this message]
2003-02-20 18:18 ` Fabrizio Nesti
2003-03-07 23:59 ` Eric Whiting
2003-03-17 17:13 ` [NFS] " Fabrizio Nesti
2003-06-05 14:49 ` Fabrizio Nesti
-- strict thread matches above, loose matches on Subject: below --
2003-02-18 17:35 Lever, Charles
2003-03-17 22:52 Wendy Cheng
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=3E53C55D.1FCF2982@amis.com \
--to=ewhiting@amis.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nesti@medialab.sissa.it \
--cc=nfs@lists.sourceforge.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.