All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Whiting <ewhiting@amis.com>
To: trond.myklebust@fys.uio.no, Jason Holmes <jholmes@psu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: Thu, 13 Nov 2003 11:59:25 -0700	[thread overview]
Message-ID: <3FB3D48D.67E9A28F@amis.com> (raw)
In-Reply-To: 16307.50555.813132.978552@charged.uio.no

Trond Myklebust wrote:
> 
>      > This is not the same test, nor the same results as Jason's, but
>      > here is some more data from bonnie and dd tests.This shows some
>      > write performance difference between 2.4 and 2.6 eric
> 
> How about vs. 2.4.23?

2.4.23 looks good -- see below -- these are acceptable numbers for a 100M
network. I reran the 2.6.0-test6-mm4 benchmarks and it still is much slower than
the the 2.4.23.

Question for Jason: -- are you running the 4/4 vm layout in your kernel? My
2.6.0-test6-mm4 has the 4/4 vm enabled -- which can have an impact on
performance. I'll tetest with 2.6.0-test9 without the mm1 and 4/4 vm enabled.

eric


Linux host 2.4.23-rc1 #2 SMP Thu Nov 13 11:30:02 MST 2003 i686 athlon i386
GNU/Linux
/test> bonnie -s 100
Writing with putc()...  done:   9228 kB/s  52.0 %CPU
Rewriting...            done:   9435 kB/s   6.0 %CPU
Writing intelligently...done:   9235 kB/s   4.0 %CPU

/test> rm file;time dd if=/dev/zero of=file bs=1 count=10000000
10000000+0 records in
10000000+0 records out

real    0m20.086s
user    0m3.120s
sys     0m16.740s


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-11-13 18:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 18:05 2.4 vs. 2.6 nfs client performance Jason Holmes
2003-11-12 20:20 ` Trond Myklebust
2003-11-12 20:51   ` Jason Holmes
2003-11-12 21:18     ` Trond Myklebust
2003-11-12 21:33       ` Jason Holmes
2003-11-12 23:22         ` Trond Myklebust
2003-11-13  1:20           ` Jason Holmes
2003-11-13  2:07             ` Trond Myklebust
2003-11-13 14:16               ` Jason Holmes
2003-11-13 21:55                 ` Jason Holmes
2003-11-14  0:22                   ` Trond Myklebust
2003-11-14 18:37                     ` Jason Holmes
2003-11-14 21:11                       ` Trond Myklebust
2003-11-16 15:54                         ` Jason Holmes
2003-11-13 15:56               ` Eric Whiting
2003-11-13 17:55                 ` Trond Myklebust
2003-11-13 18:59                   ` Eric Whiting [this message]
2003-11-13 19:09                     ` Eric Whiting
2003-11-13 19:28                       ` Trond Myklebust
2003-11-13 19:18                     ` Jason Holmes
2003-11-12 22:08 ` Eric Whiting
  -- strict thread matches above, loose matches on Subject: below --
2003-11-13 19:42 Duc Vianney
2003-11-13 20:02 ` Trond Myklebust

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=3FB3D48D.67E9A28F@amis.com \
    --to=ewhiting@amis.com \
    --cc=jholmes@psu.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.