From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: "Ruslan R. Laishev" <zator@yandex.ru>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Performance "problem" or how to get power of the DPDK
Date: Mon, 26 Dec 2022 16:07:53 +0300 [thread overview]
Message-ID: <20221226160753.11db04bb@sovereign> (raw)
In-Reply-To: <207831672055161@mail.yandex.ru>
Hi,
2022-12-26 15:20 (UTC+0300), Ruslan R. Laishev:
> I studying programming with DPDK SDK . So I write a small app to send/receive packets , now I testing it and see next situation:
> iperf3 show 9,4 - 9,7 Gbps on TCP
>
> my app can *send* only at 4+Gbps (I see counters in the rte_eth_stats) . I have tried to speed-up my app by:
> - using 1+ number of TX queues (device claim support 64)
> - increase size of burst from 32 up to 128
> - turn off any offloads related to checksumming
>
> No effect.
Please tell more about what your app does and how (w.r.t. DPDK usage).
Are you sure that all cores are loaded? E.g. if you send identical packets,
RSS can steer them all to a single queue and thus a single core.
What performance do you see using testpmd with txonly/rxonly forward mode,
if applicable?
What is the packet performance, i.e. Mpps, not Gbps, and packet size?
Unless you do TCP payload processing (or compute large payload checksums),
packets per second usually matter rather than bits per second.
next prev parent reply other threads:[~2022-12-26 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 12:20 Ruslan R. Laishev
2022-12-26 13:07 ` Dmitry Kozlyuk [this message]
2022-12-26 13:22 ` Ruslan R. Laishev
2022-12-26 19:21 ` Ruslan R. Laishev
2022-12-26 19:24 ` Ruslan R. Laishev
2022-12-26 20:04 ` Dmitry Kozlyuk
2022-12-26 20:10 ` Ruslan R. Laishev
2023-01-08 13:23 ` One transmitter worker stop after "some time" (Was: Performance "problem" or how to get power of the DPDK ) Ruslan R. Laishev
2023-01-08 17:13 ` Stephen Hemminger
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=20221226160753.11db04bb@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=users@dpdk.org \
--cc=zator@yandex.ru \
/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).