DPDK usage discussions
 help / color / mirror / Atom feed
From: Timur Bogdanov <timurbogdanov@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] The dpdk application performance degradation after moving to CentOs 7
Date: Wed, 6 Nov 2019 12:21:25 +0300	[thread overview]
Message-ID: <CAFSCPKsvOavjYEUdRGYeepfZfeg-ZN_rwnWv1DHizofG+ya4+Q@mail.gmail.com> (raw)

Hi,

I encountered with a performance degradation of my dpdk based
application after moving from RedHat 6 to CentOs 7.

Previously application was compiled with dpdk-2.2.0 library, worked on
RedHat 6 and was capable to process up to 7 Gb/s on each port of Intel
x520-sr2 NIC without packet drops.

Now application is compiled with dpdk-17.11.6 library (the application
architecture itself have not been changed), works on CentOs 7 (
3.10.0-957.el7.x86_64) and NIC drops incoming packets (imissed) if
input traffic on each port is more than 6 Gb/s. (handlers process
packets more slowly I guess )

So, hardware, input traffic, application itself has not been changed
and on both Os's application uses isolated cores, but performance
degraded.

I found an article
https://ivanvari.com/solving-poor-performance-on-rhel-and-centos-7/
and changed tuned profile from latency-performance (used on RedHat 6)
to network-latency but it didn't helped a lot.

Also I tried to turn off some security patches related to
spectre/meltdown according to article
https://access.redhat.com/articles/3311301 but it also didn't helped.

Is it possible to eliminate this performance degradation somehow or
only one possible solution is to use faster CPU's and change
application architecture (adding more handlers per port)?


/Regards, Timur

                 reply	other threads:[~2019-11-06 18:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAFSCPKsvOavjYEUdRGYeepfZfeg-ZN_rwnWv1DHizofG+ya4+Q@mail.gmail.com \
    --to=timurbogdanov@gmail.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).