From: fwefew 4t4tg <7532yahoo@gmail.com> To: users@dpdk.org Subject: Preliminary AWS ENA Benchmark Results on DPDK Date: Sun, 27 Mar 2022 20:03:46 -0400 Message-ID: <CA+Tq66USfTvFcimMANTJ9j5m86gBYd-Ey507Bn4bZO+8xLh2+Q@mail.gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 1363 bytes --] https://github.com/rodgarrison/reinvent#benchmarks I show two c5n.metal boxes with AWS ENA NICs running under DPDK in the same data center running 1 TXQ and 1 RXQ transceiving 72-byte UDP packets (32-byte payload): - transmit around 874,410 packets/sec/queue If the NIC's TXQ ring is not full the application code can hand off packets to the NICs output buffer as fast as 415 ns/pkt or some 2.4 million packets/sec. But once the TXQ ring or HW buffers get full, throughput drops about 3x. I will update the link shortly with the RX states. In short, performance seems decent except when rings are full. But since AWS ENA NICs are virtual --- they are not a bonafide NIC card plugged into the computer's PCI bus, I'm not sure if these numbers are good, average, or suck. Indeed as per: https://www.amazon.com/Data-Plane-Development-Kit-DPDK/dp/0367373955/ref=sr_1_1?keywords=data+plane+development+kit&qid=1648425589&s=books&sprefix=data+plane+devel%2Cstripbooks%2C85&sr=1-1 chapter 12 (virtio) page 236 virtio is at least partially interrupt driven. I had no idea of the details but interrupt driven surely has to under perform a vanilla case where the CPU/NIC/PCI work in unison without all the virtualization technology. I'm not even sure, by extension, whether the ENA driver is really 100% poll-driven. Any context/feedback here would be appreciated. [-- Attachment #2: Type: text/html, Size: 1771 bytes --]
reply other threads:[~2022-03-28 0:03 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=CA+Tq66USfTvFcimMANTJ9j5m86gBYd-Ey507Bn4bZO+8xLh2+Q@mail.gmail.com \ --to=7532yahoo@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
DPDK usage discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \ users@dpdk.org public-inbox-index users Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.users AGPL code for this site: git clone https://public-inbox.org/public-inbox.git