Linux NFS development
 help / color / mirror / Atom feed
From: jehan procaccia <jehan.procaccia@int-evry.fr>
To: Nicolas.Kowalski@imag.fr
Cc: nfs@lists.sourceforge.net, Joshua Baker-LePain <jlb17@duke.edu>
Subject: Re: async vs. sync
Date: Tue, 23 Nov 2004 00:51:17 +0100	[thread overview]
Message-ID: <41A27B75.4010309@int-evry.fr> (raw)
In-Reply-To: <Pine.WNT.4.61.0411222233280.1888@chalanches>

Lucky guys !
real    1m33.781s
and
tar xzf ~/tmp/httpd-2.0.52.tar.gz
real 0m25.522s
these are the kind of values I am expecting ... ( although in the 25s 
case I see that you din't used -v option of tar, which does waist lot of 
time ...) . I still cannot explain myself why I need async mode on the 
export server to appraoch these kind of performances ... ?

Nicolas.Kowalski@imag.fr wrote:

> On Mon, 22 Nov 2004, jehan procaccia wrote:
>
>> Anyone is getting the same performance as me in server sync mode ?, 
>> if someone could just tar xvfz any recent httpd.tar.gz file (nearly 
>> 3000 source files) and let me know how it take on their nfs 
>> configuration ?
>
>
> Using a 2.4.27 Linux client, without any options for the NFS mount, on 
> a 100Mbps network, I get this when untarring httpd-2.0.52.tar.gz:
>
> real    1m33.781s
> user    0m0.610s
> sys     0m0.980s
>
> Server information:
>
> - Dual-Xeon 2.4Ghz, 1GB RAM, U160 73GB SCSI disks
>
> - Linux 2.4.27, XFS filesystems, quotas (user,group) on, no ACL, sync
>   exports.
>
> Regards.
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-11-22 23:51 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 19:02 async vs. sync Lever, Charles
2004-11-22 21:25 ` jehan procaccia
2004-11-22 21:45   ` Nicolas.Kowalski
2004-11-22 23:51     ` jehan procaccia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 19:05 Lever, Charles
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 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
     [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=41A27B75.4010309@int-evry.fr \
    --to=jehan.procaccia@int-evry.fr \
    --cc=Nicolas.Kowalski@imag.fr \
    --cc=jlb17@duke.edu \
    --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