linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: quanli gui <gqlxj1987@gmail.com>
To: Benny Halevy <bhalevy@tonian.com>
Cc: linux-nfs@vger.kernel.org, "Mueller, Brian" <bmueller@panasas.com>
Subject: Re: [nfsv4]nfs client bug
Date: Thu, 30 Jun 2011 10:32:29 +0800	[thread overview]
Message-ID: <BANLkTinxF+obzedP+xupMCDZcgRTFDsQMg@mail.gmail.com> (raw)
In-Reply-To: <4E0B52BB.8090003@tonian.com>

When I use the iperf tools for one client to 4 ds, the network
throughput is 890MB/S. It reflect that it is indeed 10GE non-blocking.

a. about block size, I use bs=1M when I use dd
b. we indeed use the tcp (doesn't the nfsv4 use the tcp defaultly?)
c. the jumbo frames is what? how set mtu automatically?

Brian, do you have some more tips?


On Thu, Jun 30, 2011 at 12:28 AM, Benny Halevy <bhalevy@tonian.com> wrote:
>
> Hi,
>
> First, please use plain text only when sending to linux-nfs@vger.kernel.org
> as multi-part / html messages are automatically blocked by the spam filter.
>
> I'm not so sure that the nfs client is to blame for the performance
> you're seeing.  The problem could arise from too small of a block size
> by dd / iozone
>
> I'd try:
> a. using a larger block size (e.g.  dd bs=4096k)
> b. tuning your tcp better for high bandwidth
> c. using jumbo frames all the way, and making sure that the mtu is discovered
> automatically and set properly to 9000.
>
> Also, what's you network look like?
> what's the switch you're using
> is it indeed 10 Gbps non-blocking
> are there any linecard / chip bottlenecks or over subscription
>
> Do you see better throughput with iperf?
>
> Brian, you's probably have even more tips and tricks :)
>
> Regards,
>
> Benny
>
> On 2011-06-28 11:26, quanli gui wrote:
> > Hi,
> > Recently I test the nfsv4 speed, I found that there is something wrong in
> > the nfs client, that is the one nfs client can only provide 400MB/S to the
> > server.
> > My tests as follow:
> > machine:one client, four server; hardware: all 16core, 16G memory, 5T disk;
> > os: all suse 11 enterprise server, 2.6.31-pnfs-kernel; network: client,
> > 10GE, server, 2GE(bond, 1GE*2);
> > test method: on the client, mkdir four independent directory, mount the four
> > server via nfsv4 protocol, every time increase one;
> > test tool: iozone, or dd if=/dev/zero of=test count=20K,then cat
> > test>/dev/null
> > test result:(force on read speed, and watch the client/server network
> > input/output by the sar command)
> > 1 client vs 1 server: 200MB/S
> > 1 client vs 2 server: 380MB/S, every server: 190MB/S
> > 1 client vs 3 server: 380MB/S, every server: 130MB/S
> > 1 client vs 4 server: 385MB/S, every server: 95MB/S
> >
> > From above, we found that 400MB/S is the max-speed for one client. This
> > speed is the limition? How to increase this speed?
> >
>

  reply	other threads:[~2011-06-30  2:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTi=xcQseTx8BTWEzg-1DO=ayJuMLrw@mail.gmail.com>
2011-06-29 16:28 ` [nfsv4]nfs client bug Benny Halevy
2011-06-30  2:32   ` quanli gui [this message]
2011-06-30 13:36     ` Andy Adamson
2011-06-30 14:24       ` Trond Myklebust
2011-06-30 15:13         ` Benny Halevy
2011-06-30 15:35           ` Trond Myklebust
2011-06-30 15:42             ` Benny Halevy
2011-06-30 15:52         ` quanli gui
2011-06-30 15:57           ` Trond Myklebust
2011-06-30 16:26           ` Andy Adamson
2011-06-30 16:57             ` Ben Greear

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=BANLkTinxF+obzedP+xupMCDZcgRTFDsQMg@mail.gmail.com \
    --to=gqlxj1987@gmail.com \
    --cc=bhalevy@tonian.com \
    --cc=bmueller@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).