From: Leone Fernando <leone4fernando@gmail.com>
To: jbrouer@redhat.com, xdp-newbies@vger.kernel.org
Subject: Benchmarking Routing in Real Life Workloads
Date: Tue, 16 Apr 2024 13:23:27 +0200 [thread overview]
Message-ID: <1ab45503-e774-4227-92fb-5d30d9e7c156@gmail.com> (raw)
Hi everyone!
We encountered slowdowns in routing, and implemented a simple cache
to speed it up:
https://lore.kernel.org/netdev/20240307171202.232684-1-leone4fernando@gmail.com/
Our patch shows considerable improvement in our use-case (hundreds
of daddrs), and non-negligible improvement in other scenarios as well.
We received some pushback from the kernel community claiming this
improvement is modest in real-life scenarios.
We measured our changes using udp floods with different numbers of
daddrs. The benchmarking setup is comprised of 3 machines: a sender,
a forwarder and a receiver. We measured the PPS received by the receiver
as the forwarder was running either the mainline kernel or the patched
kernel, comparing the results.
Does anyone have a good idea for more accurate benchmarking methods?
reply other threads:[~2024-04-16 11:23 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=1ab45503-e774-4227-92fb-5d30d9e7c156@gmail.com \
--to=leone4fernando@gmail.com \
--cc=jbrouer@redhat.com \
--cc=xdp-newbies@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).