Linux NFS development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: async vs. sync
Date: Mon, 26 Jul 2004 17:17:59 +0200	[thread overview]
Message-ID: <200407261718.03264.bernd-schubert@web.de> (raw)
In-Reply-To: <200407231620.i6NGKYV20945@algebra.hillsboro.credence.com>


> On a completely seperate note, Linux-to-Linux NFS file writes
> only seem to be fast if we publish the serving Linux volume
> as asynchronous (default setting is synchronous which is slow).
>

Yeah, we just observed something similar.=20

Here some numbers for write speed of the clients:

linux-2.6.7:
async: 11MB/s
sync, wdelay: 2-3MB/s
sync, no_wdelay: 7MB/s

linux-2.4.27-rc3:
async: 11MB/s
sync, wdelay: 2-3MB/s
sync, no_wdelay: 2-3MB/s

The kernel version corresponds to the server kernel, all clients still run=
=20
2.4.26.

Unfortunality switching the server to 2.6.7 makes the server crash every=20
morning on running the cron-jobs with page allocation errors, so keeping=20
2.6.x is currently not an option. At least not as long as those errors seem=
=20
to be tolerated by the kernel maintainers :(

Any ideas whats the issue with sync vs async in 2.4.x?

Thanks,
	Bernd




=2D-=20
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2004-07-26 15:18 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 16:20 Linux NFS writes to Solaris very, very slow John Roberts
2004-07-23 16:35 ` Olaf Kirch
2004-07-26 15:17 ` Bernd Schubert [this message]
     [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
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
     [not found] <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>
2004-07-26 21:28 ` Bernd Schubert
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26 23:05 John Roberts
     [not found] <482A3FA0050D21419C269D13989C61130435E530@lavender-fe.eng.netapp.com>
2004-07-27 15:07 ` Bernd Schubert
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
2004-11-16 18:45 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-22 18:31 Lever, Charles
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 21:50 Lever, Charles
2004-11-22 22:06 ` jehan procaccia
2004-11-23  1:09 ` Dan Stromberg
     [not found] <20041122214605.8E2B31D0FE1@sc8-sf-uberspam1.sourceforge.net>
2004-11-22 21:57 ` Joshua Baker-LePain
2004-11-22 22:14 Lever, Charles
2004-11-23  3:53 Lever, Charles
2004-11-23 16:33 ` 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 16:36 Lever, Charles
2004-11-23 18:16 ` Dan Stromberg
2004-11-24 19:05 Lever, Charles

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=200407261718.03264.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --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