All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Harald Hannelius <harald+nfs@arcada.fi>
Cc: nfs@lists.sourceforge.net
Subject: Re: Poor NFS performance, kernel 2.6.6.
Date: Fri, 28 May 2004 15:55:15 +0200	[thread overview]
Message-ID: <20040528135515.GG5657@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0405280953240.29286@penti.sit.fi>

[2.6 over loopback nfs]
> real    6m21.086s
> user    0m1.712s
> sys     0m5.454s

[2.4 over loopback nfs]
> real    1m11.875s
> user    0m1.730s
> sys     0m7.730s

This roughly matches some performance issues I've been seeing on a 2.6.5
kernel. Are you using reiser or ext3?

In general, dd to a local file is much different from what NFS does,
because nfsd flushes data to disk.

The NFS client will usually issue a COMMIT call roughly every 1 Meg,
so the following should mimic the behavior of nfsd a little better,
when run on your file system locally

	iozone -s 1g -r 1m -o -i 0

Higher numbers indicate better performance.

Could you run this on 2.4 and 2.6, please?

Olaf
-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-05-28 13:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 10:31 Poor NFS performance, kernel 2.6.6 Harald Hannelius
     [not found] ` <200405271251.22746.vincent.roqueta@ext.bull.net>
2004-05-27 12:17   ` Harald Hannelius
2004-05-27 12:45     ` Vincent ROQUETA
2004-05-27 12:39 ` Dexter Filmore
2004-05-27 13:03   ` Harald Hannelius
2004-05-27 18:07 ` Bernd Schubert
2004-05-27 19:01   ` Trond Myklebust
2004-05-27 20:56   ` Harald Hannelius
2004-05-27 22:09 ` Trond Myklebust
2004-05-28  7:17   ` Harald Hannelius
2004-05-28 13:55     ` Olaf Kirch [this message]
2004-05-28 16:57       ` Phy Prabab
2004-05-28 18:03       ` Harald Hannelius
2004-05-28 19:19         ` Trond Myklebust
2004-06-01  0:16           ` Yusuf Goolamabbas
2004-06-02  6:57             ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27 13:16 Harald Hannelius
2004-06-02 12:33 Jeffrey Layton
2004-06-02 13:00 ` Greg Banks
2004-06-02 13:40   ` Jeffrey Layton
2004-06-02 13:14 ` Vincent ROQUETA
2004-06-02 14:53 ` Jeffrey Layton

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=20040528135515.GG5657@suse.de \
    --to=okir@suse.de \
    --cc=harald+nfs@arcada.fi \
    --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.