From: Patrick Mahan <mahan@mahan.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Best example for showing throughput?
Date: Fri, 24 May 2013 11:51:09 -0700 [thread overview]
Message-ID: <5BBC85C7-B39F-4200-AB7B-CD5464BDA431@mahan.org> (raw)
In-Reply-To: <201305241745.25844.thomas.monjalon@6wind.com>
On May 24, 2013, at 8:45 AM, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> Adding other questions about packet generator:
>
> 24/05/2013 16:41, Thomas Monjalon :
>> 24/05/2013 16:11, Patrick Mahan :
>>> Intel Xeon E5-2690 (8 physical, 16 virtual)
>>
>> How many CPU sockets have you ?
>>
>>> 64 Gbyte DDR3 memory
>>> Intel 82599EB-SPF dual port 10GE interface
>>> CentOS 6.4 (2.6.32-358.6.1.el6.x86_64)
>>> The 82599 is in a 16x PCI-e slot.
>>
>> Check the datasheet of your motherboard.
>> Are you sure it is wired as a 16x PCI-e ?
>> Is it connected to the right NUMA node ?
>>
>>> I have it attached to an IXIA box.
>
> Which packet size are you sending with your packet generator ?
> In case of 64 byte packets (with Ethernet CRC), (64+20)*8 = 672 bits.
> So line rate is 10000/672 = 14.88 Mpps.
> This bandwith should be supported by your 82599 NIC.
Yes, the Ixia is sending the standard 64 byte packet. The stats show a send rate of 14.880 Mpps.
>
> Are you sending and receiving on the 2 ports at the same time ?
> Forwarding in the 2 directions is equivalent to double the bandwidth.
> Maybe that 14.88*2 = 29.76 Mpps is too much for your hardware.
>
Yes I am running traffic both ways. Interestingly, the amount of drops seem consistent in both directions. This makes sense since testpmd is spinning off a thread to read from each input queue.
> You could also try with 2 ports on 2 different NICs.
Hmmm, not sure if I can lay hands on another 82599 card. This one is a loaner.
Thanks,
Patrick
>
>>> I have been running the app 'testpmd'
>>> in iofwd mode with 2K rx/tx descriptors and 512 burst/mbcache. I have
>>> been varying the # of queues and unfortunately, I am not seeing full
>>> line rate.
>>
>> What is your command line ?
>>
>>> I am seeing about 20-24% droppage on the receive side. It doesn't seem
>>> to matter the # of queues.
>>
>> If queues are polled by different cores, it should matter.
>>
>>> Question 1: Is 'testpmd' the best application for this type of testing?
>>> If not, which program? Or do I need to roll my own?
>>
>> testpmd is the right application for performance benchmark.
>> It is also possible to use examples l2fwd/l3fwd but you should keep
>> testpmd.
>>
>>> Question 2: I have blacklisted the Intel i350 ports on the motherboard
>>> and am using ssh to access the platform. Could this be affecting the
>>> test?
>>
>> You mean i350 is used for ssh ? It shouldn't significantly affect your
>> test.
>
> --
> Thomas
next prev parent reply other threads:[~2013-05-24 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 14:11 Patrick Mahan
2013-05-24 14:41 ` Thomas Monjalon
2013-05-24 15:45 ` Thomas Monjalon
2013-05-24 18:51 ` Patrick Mahan [this message]
2013-05-25 19:23 ` Damien Millescamps
2013-05-25 20:59 ` Damien Millescamps
2013-05-28 19:15 ` Patrick Mahan
2013-05-29 14:07 ` Damien Millescamps
2013-05-29 18:24 ` Patrick Mahan
2013-05-24 18:32 ` Patrick Mahan
2013-05-24 20:03 ` Olivier MATZ
2013-05-24 20:44 ` Patrick Mahan
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=5BBC85C7-B39F-4200-AB7B-CD5464BDA431@mahan.org \
--to=mahan@mahan.org \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).