From: Eric Whiting <ewhiting@amis.com>
To: trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: 2.4 vs. 2.6 nfs client performance
Date: Thu, 13 Nov 2003 12:09:32 -0700 [thread overview]
Message-ID: <3FB3D6EC.E4F1FF17@amis.com> (raw)
In-Reply-To: 3FB3D48D.67E9A28F@amis.com
Eric Whiting wrote:
>
> 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?
>
> I'll tetest with 2.6.0-test9 without the mm1 and 4/4 vm enabled.
>
2.6.0-test9 (without mm1 4/4 vm) is even worse than 2.6.0-test6-mm4.
tcpdump shows very slow writes..
12:07:12.380001 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33858:1480@0+)
12:07:12.380012 172.16.17.176 > 172.16.32.181: udp (frag 33858:1480@1480+)
12:07:12.380014 172.16.17.176 > 172.16.32.181: udp (frag 33858:1284@2960)
12:07:17.979092 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33859:1480@0+)
12:07:17.979102 172.16.17.176 > 172.16.32.181: udp (frag 33859:1480@1480+)
12:07:17.979104 172.16.17.176 > 172.16.32.181: udp (frag 33859:1284@2960)
12:07:18.678981 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33860:1480@0+)
12:07:18.678992 172.16.17.176 > 172.16.32.181: udp (frag 33860:1480@1480+)
12:07:18.678994 172.16.17.176 > 172.16.32.181: udp (frag 33860:1284@2960)
12:07:20.078755 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33861:1480@0+)
12:07:20.078766 172.16.17.176 > 172.16.32.181: udp (frag 33861:1480@1480+)
12:07:20.078768 172.16.17.176 > 172.16.32.181: udp (frag 33861:1284@2960)
12:07:22.879310 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33862:1480@0+)
12:07:22.879321 172.16.17.176 > 172.16.32.181: udp (frag 33862:1480@1480+)
12:07:22.879323 172.16.17.176 > 172.16.32.181: udp (frag 33862:1284@2960)
12:07:28.479388 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33863:1480@0+)
12:07:28.479399 172.16.17.176 > 172.16.32.181: udp (frag 33863:1480@1480+)
12:07:28.479400 172.16.17.176 > 172.16.32.181: udp (frag 33863:1284@2960)
12:07:29.179275 172.16.17.176.1525633085 > 172.16.32.181.2049: 1472 write [|nfs]
(frag 33864:1480@0+)
12:07:29.179286 172.16.17.176 > 172.16.32.181: udp (frag 33864:1480@1480+)
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-11-13 19:08 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
2003-11-13 19:09 ` Eric Whiting [this message]
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=3FB3D6EC.E4F1FF17@amis.com \
--to=ewhiting@amis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox