From: Thomas Monjalon <thomas@monjalon.net>
To: Anand Prasad <anandnprasad@yahoo.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] DPDK Performance tips
Date: Wed, 13 Dec 2017 12:11:10 +0100 [thread overview]
Message-ID: <4438207.qMLY8BktU0@xps> (raw)
In-Reply-To: <401616826.3643255.1513152888444@mail.yahoo.com>
13/12/2017 09:14, Anand Prasad:
> Hi Dpdk team,
> Can anyone please share tips to get better DPDK performance? I have tried to run DPDK test applications on various PC configurations with different CPU Speeds, RAM Size/Speed and and PCIex16 2nd and 3rd generation connections... but I don't get very consistent results.
> The same test application does not behave similarly on 2 PC's with same hardware configuration.But general observation is that, performance is better on Intel motherboard with 3rd generation PCIe slot. When tried on Gigabyte motherboard (even with higher CPU and RAM speeds), performance was very poor.
> The performance issue I am facing is the Packet Drop issue on the Rx side.
> Two PC's with exactly same hardware configuration, one PC drops packets after few hours, but in the other PC I don't observe packet drop
> Highly appreciate a quick response
> Regards,Anand Prasad
This is very complicate because it really depends on the hardware.
Managing performance requires a very good knowledge of the hardware.
You can find some basic advices in this guide for some Intel hardware:
http://dpdk.org/doc/guides/linux_gsg/nic_perf_intel_platform.html
You will also find some informations in the drivers guide. Example:
http://dpdk.org/doc/guides/nics/mlx5.html#performance-tuning
next prev parent reply other threads:[~2017-12-13 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <401616826.3643255.1513152888444.ref@mail.yahoo.com>
2017-12-13 8:14 ` Anand Prasad
2017-12-13 11:11 ` Thomas Monjalon [this message]
2018-02-19 14:26 ` Anand Prasad
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=4438207.qMLY8BktU0@xps \
--to=thomas@monjalon.net \
--cc=anandnprasad@yahoo.com \
--cc=users@dpdk.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).