All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: "Lever, Charles" <cel@netapp.com>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: async vs. sync
Date: Mon, 26 Jul 2004 23:28:00 +0200	[thread overview]
Message-ID: <200407262328.07704.bernd-schubert@web.de> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]

On Monday 26 July 2004 19:21, you wrote:
> sorry i'm not copying the list... our local exchange server changed my
> outgoing To: address a couple of weeks ago, and i still haven't gotten
> the list moderator's attention to fix up my e-mail address.

No problem, I will send a full quote to the list.

>
> > Exactly, therefore I would like to enable the sync-export
> > option again.
> > However, reducing the speed to about 1/5 of async speed for
> > large files and
> > to about 1/20 for smaller files is not an option. The people already
> > complained that compiling their projects takes ages now...
> >
> > D'oh, sorry, I forgot to write that we use the tcp-mounts and
> > nfs3. So  those
> > numbers really shouldn't happen, should they?
>
> if the server is working correctly, theoretically this should not
> happen.
>
> are you using strange mount options on the client, such as "noac" or
> "sync" ?  "async" on the client is perfectly OK to use; it's the server
> side export option that is badness.

No, I think not. Here's the fstab line for /home:
hamilton:/home /home  nfs rsize=8192,wsize=8192,hard,intr,tcp  0  0

Here's something that is for me pretty interesting (since I don't completely 
understand whats causing it):

1.) The export option is changed on the server from sync to async, 
'exportfs -rav' is executed.

2.) One client had mounted with the async-mount option, all other clients 
without this option. No client remounts /home after the the export option was 
changed on the server.

3.) All but the one client now can write to the server with 5MB/s for large 
*and* small files. However the client which has mounted with the async-mount 
option can now write with full 100MBit (so 11 MB/s) to the server.

4.) Of course, remounting /home on any client even without giving the 
async-mount option, gives back full write speed to all clients now.

Is the behaviour from 3) intented to happen? Actually I thought that a remount 
on the clients is necessary to gain back full write speed.

Thanks,
	Bernd

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2004-07-26 21:28 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>
2004-07-26 21:28 ` Bernd Schubert [this message]
2004-11-24 19:05 async vs. sync 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] <482A3FA0050D21419C269D13989C61130435E51E@lavender-fe.eng.netapp.com>
2004-07-26 17:05 ` 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
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-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=200407262328.07704.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=cel@netapp.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 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.