All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Some NFS performance numbers for 2.6.31
Date: Thu, 24 Sep 2009 11:06:41 -0700	[thread overview]
Message-ID: <4ABBB531.2050103@candelatech.com> (raw)
In-Reply-To: <20090924175439.GA10385@fieldses.org>

On 09/24/2009 10:54 AM, J. Bruce Fields wrote:
> On Wed, Sep 23, 2009 at 04:48:21PM -0700, Ben Greear wrote:
>> On 09/22/2009 05:42 PM, Ben Greear wrote:
>>> I'm running some performance tests on NFSv3 on a slightly hacked 2.6.31
>>> kernel.
>>
>> I realized that LRO on the NICs was disabled because I had enabled ip-forwarding.
>>
>> I re-enabled that, and now can get about 18Gbps read rates (on the wires), using MTU
>> 1500.
>
> On a 10 gig nic?  (Oh, sorry, I see: 2 10 gig nics.  OK!)  Just out of
> curiosity: have you done any testing with real drives?  Which kernel is
> this?

I see similar performance on real drivers, but I haven't done any tests with *only*
using physical drivers.  Since that would exercise only a single mount, I'm
not sure if it would scale as well as using multiple mounts with multiple
virtual interfaces, but that is just pure hypothesizing on my part.

This is 2.6.31 kernel, 64-bit, most kernel related debugging disabled.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2009-09-24 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  0:42 Some NFS performance numbers for 2.6.31 Ben Greear
2009-09-23 23:48 ` Ben Greear
2009-09-24 17:54   ` J. Bruce Fields
2009-09-24 18:06     ` Ben Greear [this message]

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=4ABBB531.2050103@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bfields@fieldses.org \
    --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 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.