netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Thery <benjamin.thery@bull.net>
To: Rick Jones <rick.jones2@hp.com>
Cc: Daniel Lezcano <dlezcano@fr.ibm.com>,
	Linux Containers <containers@lists.osdl.org>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: network namespace ipv6 perfs
Date: Tue, 04 Mar 2008 16:59:56 +0100	[thread overview]
Message-ID: <47CD71FC.6010504@bull.net> (raw)
In-Reply-To: <47CC590E.5070907@fr.ibm.com>

Daniel Lezcano wrote:
> Rick Jones wrote:
>> Daniel Lezcano wrote:
>>> Hi,
>>>
>>> Some performance tests was made by Benjamin to watch out the impact 
>>> of the network namespace. The good news is there is no impact when 
>>> used with or without namespaces. That has been checked using a real 
>>> network device inside a network namespace.
>>
>> The *_RR tests seem to show a drop in througput and corresponding 
>> increases in service demand - could that be because things like TSO et 
>> al cannot mask much of anything in the way of a path-length increase?
> 
> Hmm. In fact Benjamin took the 2.6.23.16 kernel where there were no 
> network namespace code at all. So these differences between 2.6.23.16 
> and 2.6.25-rc1 does not show a performance degradation especially 
> related to the network namespaces. The important point is the 2.6.25-rc1 
> without ipv6 netns and 2.6.25-rc1 with ipv6 netns code applied, I mean 
> the second and the third line and we can point that the ipv6 netns code 
> does not degrade performances for either throughput and service demand.

As Daniel stated, we should not compare the first bar with the other
ones directly. May be I should have arranged the chart differently and
made it more clear that the first bar is "2.6.23 vanilla" and the second
one is "2.6.25-rc1 vanilla". Many changes happened in the whole kernel
between 2.6.23 and 2.6.24 so we can't compare the first two bars to tell
if network namespace degraded performances (and only a small part of
netns is in 2.6.24).
The way I presented the chart is a bit misleading. :)

What's interesting to compare in the charts is the 2nd, 3rd and 4th
lines. It shows that on the exact same hardware (in the 4th case the
physical interface is moved into the child namespace), with or without
the patchset, using network namespace or not, performance is about the
same.

Benjamin

>>  From the annotations, I'm ass-u-me-ing that NS was only used on the 
>> netperf side and not both netperf and netserver side?
> 
> right :)
> 
>> happy benchmarking,
> 
> Thanks Rick.
> 
>   -- Daniel
> 
> 


-- 
B e n j a m i n   T h e r y  - BULL/DT/Open Software R&D

    http://www.bull.com

      reply	other threads:[~2008-03-04 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 14:20 network namespace ipv6 perfs Daniel Lezcano
2008-03-03 14:42 ` Benjamin Thery
2008-03-03 14:55   ` [Devel] " Pavel Emelyanov
2008-03-03 15:04     ` Benjamin Thery
2008-03-03 17:27       ` Benjamin Thery
2008-03-05 12:39         ` Pavel Emelyanov
2008-03-03 14:48 ` Benjamin Thery
2008-03-03 19:38 ` Rick Jones
2008-03-03 20:01   ` Daniel Lezcano
2008-03-04 15:59     ` Benjamin Thery [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=47CD71FC.6010504@bull.net \
    --to=benjamin.thery@bull.net \
    --cc=containers@lists.osdl.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    /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).