All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Whiting <ewhiting@amis.com>
To: Fabrizio Nesti <nesti@medialab.sissa.it>
Cc: Alan Powell <lakerfaniam2@yahoo.com>, nfs@lists.sourceforge.net
Subject: Re: 2.4.20 TCP server + solaris client performance
Date: Tue, 18 Feb 2003 08:29:58 -0700	[thread overview]
Message-ID: <3E525176.13DFBBA1@amis.com> (raw)
In-Reply-To: Pine.GSO.4.40.0302181044060.26640-100000@bodoni

Have you verified that your storage is properly setup? Is it IDE/SCSI/RAID? IDE
storage with DMA disabled will cause terrible performance. Please verify disk
speed on local writes and make sure they are 'faster' than the network. 

What version of SOlaris are you running? Solaris 8 and newer has a lot of NFS
fixes...

We are getting good NFS numbers with 2.4.20 UDP NFS servers against solaris [89]
clients.

eric





Fabrizio Nesti wrote:
> 
> Sorry,
> the reason to switch to TCP was exactly the same: poor nfs performance as
> seen from any solaris client. And by poor I mean three-five times slower.
> 
> The same "tar xf" (a typical high load r/w usage) gives
> 
>                      linux server           solaris server
> linux   client      1 sec (udp)(caching?)    8 sec (for both tcp and udp)
> solaris client      22/40 sec (tcp/udp)      10/8 sec (tcp/udp)
> 
> We worry about these ^^^  figures, since we bought a new linux server
> to switch to, and we have some solaris clients.
> 
> Since solaris nfs clients sseems to prefer TCP, and following some messages
> on the list, we tried that. (Even tuning can not improve this situation).
> Is there something wrong we are doing or we have to switch back to soalris
> server?
> 
> Thanks again,
> Fabrizio Nesti
> 
> On Mon, 17 Feb 2003, Alan Powell wrote:
> 
> > 8192 block size is a Linux daemon limitation. Also,
> > don't switch to TCP unless you need to. UDP will be
> > faster if you have a decent network. Revert back to
> > UDP, and on the client side, run "nfsstat -c" and
> > monitor the number of retransmissions. If that number
> > doesn't increase, you have a clean network, and you
> > should stay on UDP.
> >
> >
> > --- Fabrizio Nesti <nesti@medialab.sissa.it> wrote:
> > > Hello to everybody.
> > > we are reporting a very low performance for nfs
> > > access from Solaris clients
> > > to the linux nfs server on RH8.0. We thought it was
> > > udp and upgraded to
> > > kernel 2.4.20.
> > >
> > > Now the performance is still low, compared to a
> > > solaris server:
> > >     # time gtar xf /var/tmp/cvs-1.11.5.tar
> > >     Writing on Linux_2.4.20> real    0m22.132s
> > >     Writing on Solaris_8>    real    0m7.174s
> > >
> > > Both filesystems are mounted with
> > > proto=tcp,rsize=32768,wsize=32768.
> > > Snooping the traffic however, it appears that the
> > > linux server is not
> > > serving with size=32768, but with a maximum size of
> > > 8192.
> > >
> > > - Is there a reson for this?
> > > - May this be the reason for the poor performance
> > > above?
> > >
> > > Thanks in advance,
> > > Fabrizio Nesti
> > >
> > >
> > > PS: Some snoop traffic:
> > > ...
> > >   solaris -> linux  NFS C CREATE3 FH=884D
> > > (EXCLUSIVE) check_cvs.in
> > > linux -> solaris    NFS R CREATE3 OK FH=174A
> > >  solaris -> linux   NFS C SETATTR3 FH=174A
> > > linux -> solaris    NFS R SETATTR3 OK
> > >   solaris -> linux  NFS C WRITE3 FH=174A at 0 for
> > > 8192 (ASYNC)
> > >   solaris -> linux  TCP D=2049 S=793 Ack=633960980
> > > Seq=849797604 Len=1460
> > >   solaris -> linux  TCP D=2049 S=793 Ack=633960980
> > > Seq=849799064 Len=1460
> > >   solaris -> linux  TCP D=2049 S=793 Ack=633960980
> > > Seq=849800524 Len=1460
> > >   solaris -> linux  TCP D=2049 S=793 Ack=633960980
> > > Seq=849801984 Len=1460
> > >   solaris -> linux  TCP D=2049 S=793 Ack=633960980
> > > Seq=849803444 Len=1056
> > > linux -> solaris    TCP D=793 S=2049 Ack=849804500
> > > Seq=633960980 Len=0
> > > ...
> > >
> > >
> > >
> > >
> > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > NFS maillist  -  NFS@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nfs
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Shopping - Send Flowers for Valentine's Day
> > http://shopping.yahoo.com
> >
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-02-18 15:30 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 [this message]
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
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=3E525176.13DFBBA1@amis.com \
    --to=ewhiting@amis.com \
    --cc=lakerfaniam2@yahoo.com \
    --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.