From: Bernd Schubert <bernd-schubert@web.de>
To: Jan Bruvoll <jan@bruvoll.com>
Cc: NFS mailling list <nfs@lists.sourceforge.net>
Subject: Re: async vs. sync
Date: Tue, 27 Jul 2004 15:00:31 +0200 [thread overview]
Message-ID: <200407271500.38074.bernd-schubert@web.de> (raw)
In-Reply-To: <410643C5.3040004@bruvoll.com>
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
> >>My set-up has about the same performance data, however my big problem is
> >>that the server dies when I hook all my clients up... Raw throughput
> >
> >Fortunately that doesn't seem to happen in our case.
>
> Let me clarify - the server doesn't quite die, however it slows down
> drastically, having a load of ~7 while 99% CPU idle. The clients clog
> up, and for instance trying to mount anything just times out. If I
> unmount the busy share from the clients, everything settles down again.
We noticed a higher load with sync-mounts, usually we have 0-2, with 2.4. and
sync-mounts it went until 3-4. But we also only used sync mounts for less
than 24, so changed to async mounts as soon as the people complained.
[snip]
>
> I tried a little more performance number hunting:
> - NFS copy and write to same device - 3Mb/s sustained (500Mb file)
> - piozone direct write to RAID device - ~34-50Mb/s (depending on file
> size) - drbd network device - 933Mb/s
>
> Nothing really wrong here I'd say - not blazingly quick, but surely
> nothing to explain why everything just stops when I hook up my 12
> clients to this set-up?
Certainly not. We have 45 diskless booting clients.
[snip]
> >Well, as I said, when I tested our old server with sync mounts, it had the
> >same problem. Are you sure that your old server did not export
> > asynchronous?
>
> Doesn't seem so, no, the /etc/export is -extremely- simple:
>
> /export client1(rw,no_root_squash)
Which nfs-utils version is running on that server? With 1.0 the default
changed from async to sync. I guess you only did security updates from your
distribution and so there's <=0.3 installed.
With 2.6.7 it helped us a lot to give the no_wdelay option, maybe you should
try it as well.
>
> Similarly, I'm not trying to be clever on the client side (/etc/fstab
> excerpt):
>
> server:/export /export nfs rw,hard,intr 0 0
You should make sure, that rsize and wsize are set to 8192 (cat /proc/mounts
tells you the current value). Also, just try to use tcp-mounts, if you have
an asynchronous net (e.g. the server and switch have a GBit interface, but
the clients only 100MBit) this is necessary anyway. The same if the clients
or server are using linux-2.6.x.
Cheers,
Bernd
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-27 13:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <482A3FA0050D21419C269D13989C61130435E51E@lavender-fe.eng.netapp.com>
2004-07-26 17:05 ` async vs. sync Bernd Schubert
2004-07-26 19:47 ` Jan Bruvoll
2004-07-26 22:06 ` Bernd Schubert
2004-07-27 12:00 ` Jan Bruvoll
2004-07-27 13:00 ` Bernd Schubert [this message]
2004-07-27 13:56 ` raven
2004-07-27 14:04 ` Jan Bruvoll
2004-07-27 14:11 ` Jan Bruvoll
2004-07-28 8:56 ` Olaf Kirch
2004-07-28 12:35 ` Bernd Schubert
2004-07-28 12:49 ` Olaf Kirch
2004-11-24 19:05 Lever, Charles
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 16:36 Lever, Charles
2004-11-23 18:16 ` Dan Stromberg
2004-11-23 14:30 Lever, Charles
2004-11-23 21:46 ` jehan procaccia
2004-11-24 18:45 ` jehan.procaccia
2004-11-24 22:24 ` Neil Brown
2004-11-24 23:14 ` jehan procaccia
2004-11-24 23:34 ` Neil Brown
2004-11-24 22:09 ` Neil Brown
[not found] ` <Pine.GSO.4.53.0412010900500.5486@int1.cdc.noaa.gov>
2004-12-01 17:27 ` jehan.procaccia
2004-11-23 3:53 Lever, Charles
2004-11-23 16:33 ` Dan Stromberg
2004-11-22 22:14 Lever, Charles
[not found] <20041122214605.8E2B31D0FE1@sc8-sf-uberspam1.sourceforge.net>
2004-11-22 21:57 ` Joshua Baker-LePain
2004-11-22 21:50 Lever, Charles
2004-11-22 22:06 ` jehan procaccia
2004-11-23 1:09 ` Dan Stromberg
2004-11-22 19:02 Lever, Charles
2004-11-22 21:25 ` jehan procaccia
2004-11-22 21:45 ` Nicolas.Kowalski
2004-11-22 23:51 ` jehan procaccia
2004-11-22 18:31 Lever, Charles
2004-11-16 18:48 Lever, Charles
2004-11-22 15:36 ` Olaf Kirch
2004-11-22 17:55 ` jehan.procaccia
2004-11-22 18:06 ` Roger Heflin
2004-11-22 18:46 ` jehan.procaccia
2004-11-22 19:10 ` Roger Heflin
2004-11-22 21:44 ` jehan procaccia
2004-11-22 21:52 ` jehan procaccia
2004-11-22 22:20 ` Trond Myklebust
2004-11-22 22:57 ` jehan procaccia
2004-11-23 9:50 ` jehan procaccia
2004-11-23 14:57 ` J. Bruce Fields
2004-11-22 18:08 ` Trond Myklebust
2004-11-22 18:57 ` jehan.procaccia
2004-11-22 19:05 ` Roger Heflin
2004-11-22 20:14 ` Trond Myklebust
2004-11-22 21:04 ` Paul Cunningham
2004-11-22 21:14 ` Trond Myklebust
2004-11-22 22:07 ` Paul Cunningham
2004-11-22 22:26 ` Trond Myklebust
2004-11-16 18:45 Lever, Charles
2004-11-16 16:15 Lever, Charles
2004-11-16 16:32 ` Trond Myklebust
2004-11-16 17:18 ` jehan.procaccia
2004-11-16 18:08 ` Trond Myklebust
[not found] <482A3FA0050D21419C269D13989C61130435E530@lavender-fe.eng.netapp.com>
2004-07-27 15:07 ` Bernd Schubert
2004-07-26 23:05 John Roberts
[not found] <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>
2004-07-26 21:28 ` Bernd Schubert
2004-07-23 16:20 Linux NFS writes to Solaris very, very slow John Roberts
2004-07-26 15:17 ` async vs. sync Bernd Schubert
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=200407271500.38074.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=jan@bruvoll.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox