base on dperf: High-Performance Network Load Testing Tool Based on DPDK # dperf [](https://github.com/baidu/dperf/blob/main/LICENSE) [](https://chat.openai.com/) <a href="https://hellogithub.com/repository/67958cc5d1f44a6a84f3544e3c007e5f" target="_blank"><img src="https://abroad.hellogithub.com/v1/widgets/recommend.svg?rid=67958cc5d1f44a6a84f3544e3c007e5f&claim_uid=Thc9mJByaKSbdng&theme=small" alt="Featured｜HelloGitHub" /></a> **dperf** is a high-performance network traffic generator and load testing tool based on **DPDK**. ## Advantages - **High Performance** Built on DPDK, dperf can generate massive traffic using a single x86 server — achieving tens of millions of HTTP Connections Per Second (CPS), hundreds of Gbps throughput, and billions of concurrent connections. - **Comprehensive Statistics** Provides detailed real-time metrics and identifies every packet drop or error. - **Versatile Use Cases** - Load and stability testing for Layer 4 Load Balancers and gateways - Network performance benchmarking for cloud servers - Evaluation of NIC and CPU packet processing capabilities - Acts as a high-performance HTTP server or client for testing scenarios ## Performance All results were measured using the following hardware and configuration: - **CPU**: Intel Xeon Gold 5418Y × 2 - **Memory**: 128 GB × 2 - **NIC**: Intel E810-C Dual-Port 100GbE × 2 - **OS**: Linux 5.10.0 ### HTTP Connections Per Second (CPS) | Client Cores | Server Cores | HTTP CPS (Million) | Client CPU Usage (%) | Server CPU Usage (%) | |--------------|---------------|-------------------|----------------------|----------------------| | 1 | 1 | 4 | 74 | 71 | | 2 | 2 | 8 | 74 | 72 | | 4 | 4 | 16 | 73 | 70 | | 8 | 8 | 32 | 70 | 68 | | 16 | 16 | 64 | 70 | 68 | ### HTTP Throughput (Gbps) | Client Cores | Server Cores | RX Throughput | TX Throughput | Client CPU Usage (%) | Server CPU Usage (%) | |--------------|--------------|---------------|---------------|----------------------|----------------------| | 1 | 1 | 98.3 Gbps | 98.3 Gbps | 78 | 80 | | 2 | 2 | 196.7 Gbps | 196.7 Gbps | 78 | 82 | ### Concurrent Connections | Client Cores | Server Cores | Connections (Billion) | Client CPU Usage (%) | Server CPU Usage (%) | Memory Usage (GB) | |--------------|--------------|-----------------------|----------------------|----------------------|-------------------| | 1 | 1 | 1 | 48 | 48 | 60 | | 2 | 2 | 2 | 48 | 48 | 120 | | 4 | 4 | 4 | 48 | 48 | 240 | ### TCP Packets Per Second (PPS) | Client Cores | RX PPS (Mpps) | TX PPS (Mpps) | Client CPU Usage (%) | |--------------|---------------|---------------|----------------------| | 1 | 16.8 | 16.8 | 99 | | 6 | 105.2 | 105.2 | 99 | | 12 | 204.6 | 204.6 | 99 | ## Real-Time Statistics dperf prints real-time statistics every second, including CPS, TPS, PPS, packet drops, socket errors, and HTTP status counts. Example output: ```plaintext seconds 22 cpuUsage 52 pktRx 3,001,058 pktTx 3,001,025 bitsRx 2,272,799,040 bitsTx 1,920,657,600 dropTx 0 arpRx 0 arpTx 0 icmpRx 0 icmpTx 0 otherRx 0 badRx 0 synRx 1,000,345 synTx 1,000,330 finRx 1,000,350 finTx 1,000,350 rstRx 0 rstTx 0 synRt 0 finRt 0 ackRt 0 pushRt 0 tcpDrop 0 skOpen 1,000,330 skClose 1,000,363 skCon 230 skErr 0 httpGet 1,000,345 http2XX 1,000,350 httpErr 0 ierrors 0 oerrors 0 imissed 0 ``` ## Documentation See the official website at [https://dperf.org/](https://dperf.org/). ## Contributing We welcome contributions! Please see the [CONTRIBUTING](CONTRIBUTING.md) file for details. ## Patent - **Title**: Testing Method and Apparatus for Network Devices - **Inventor**: Jianzhang Peng - **Patent Number**: CN114205274B - **Issue Date**: June 11, 2024 ## Acknowledgment We gratefully acknowledge [xnetin](https://www.xnetin.com/) for providing the high-performance testing platform used in our benchmarking experiments. ## Author **[Jianzhang Peng](https://github.com/pengjianzhang)** holds a Ph.D. in Computer Science from the University of Science and Technology of China (USTC). He previously worked as a Principal Engineer at Baidu, where he contributed to the development of high-performance L4 load balancer systems. He initiated and developed the dperf project during his time at Baidu, and continues to maintain it as an open-source contributor. His current focus is on low-latency network protocol stacks for quantitative trading systems. ## License dperf is licensed under the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0). ", Assign "at most 3 tags" to the expected json: {"id":"4770","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"