netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevich@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>, netdev <netdev@vger.kernel.org>
Subject: Re: SCTP performance?
Date: Mon, 12 Aug 2013 16:10:39 -0400	[thread overview]
Message-ID: <5209413F.7090802@gmail.com> (raw)
In-Reply-To: <520583AB.9030509@candelatech.com>

On 08/09/2013 08:04 PM, Ben Greear wrote:
> On 08/09/2013 04:21 PM, Eric Dumazet wrote:
>> On Fri, 2013-08-09 at 16:11 -0700, Ben Greear wrote:
>>> I just added some support for SCTP to my traffic-generator tool.
>>>
>>> I tried to send 1Gbps of traffic, bi-directional, across two
>>> 10G interfaces.  TCP does this without any trouble at all,
>>> but SCTP was asymetric and never got above around 700Mbps,
>>> and was usually stuck at < 500Mbps.
>>>
>>> perf top didn't show any obvious CPU bottlenecks.
>>>
>>> Has anyone done any recent performance testing with SCTP?
>>>
>>> I'd be interested to know the results if so...
>>
>> You mean there is no SCTP offload on the NIC and/or GRO, yes that's too
>> bad.
>>
>
> I'm sure that is part of the problem.
>
> I got much better results when I explicitly set the
> tx/rx socket buffer sizes to 2MB, so maybe it just sucks
> at auto-tuning it's socket buffer sizes.
>
> Thanks,
> Ben
>

There is no buffer autotunning.  There is also no GRO since SCTP doesn't
lend itself easily to GRO. :(

There has been some research efforts at autotunning, but nothing 
proposed.  I'll see if I can find the code and make it work better.

-vlad

      parent reply	other threads:[~2013-08-12 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 23:11 SCTP performance? Ben Greear
2013-08-09 23:21 ` Eric Dumazet
2013-08-10  0:04   ` Ben Greear
2013-08-10  0:54     ` David Miller
2013-08-12 20:10     ` Vlad Yasevich [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=5209413F.7090802@gmail.com \
    --to=vyasevich@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=netdev@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).