Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • D dns-probe
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • adam
  • dns-probe
  • Wiki
  • Performance tests for DNS Probe 0.5.0

Performance tests for DNS Probe 0.5.0 · Changes

Page history
Create Performance tests for DNS Probe 0.5.0 authored Jul 01, 2020 by Pavel Doležal's avatar Pavel Doležal
Hide whitespace changes
Inline Side-by-side
Performance-tests-for-DNS-Probe-0.5.0.md 0 → 100644
View page @ 05db328b
## Test configuration
Performance testing was done on a server with following specifications:
* **CPU**: Intel Xeon E5-2620@2.00 GHz
* **RAM**: 32 GB DDR3@1600 Mhz
* **OS**: Debian, linux kernel 5.4.0
* **NIC**: Intel X-520-2, 2x 10 Gb
DNS traffic to this server was generated and sent by Spirent TestCenter SPT-2000A through a 10 Gbps line.
All DNS traffic was sent over UDP with 33% of queries and responses containing EDNS record.
DNS Probe was run with default Sysrepo configuration with only `export-format` changed to `cdns` when measuring C-DNS performance and `coremask` changed to correspond with the number of packet processing threads shown in the table in section [Test results](#test-results).
## Test results
The following table contains results of the performance tests for DNS Probe. DNS Probe was run in four
different configurations depending on the packet processing backend and export format used.
| Probe configuration (pkts/s) / Packet processing threads | 1 | 2 | 4 |
|----------------------------------------------------------|---|---|---|
| DPDK - Parquet | 718 000 | 1 441 000 | 2 647 000 |
| DPDK - C-DNS | 1 420 000 | 2 739 000 | 5 176 000 |
| AF_PACKET - Parquet | 487 000 | 780 000 | 1 350 000 |
| AF_PACKET - C-DNS | 805 000 | 1 242 000 | 2 017 000 |
The following table contains the same measurements as the table above, only with the numbers converted
to Gbps.
| Probe configuration (Gbps) / Packet processing threads | 1 | 2 | 4 |
|--------------------------------------------------------|---|---|---|
| DPDK - Parquet | 1,20 | 2,42 | 4,44 |
| DPDK - C-DNS | 2,38 | 4,60 | 8,69 |
| AF_PACKET - Parquet | 0,81 | 1,31 | 2,26 |
| AF_PACKET - C-DNS | 1,35 | 2,00 | 3,39 |
\ No newline at end of file
Clone repository
  • CDNS_PCAP_sizes
  • Home
  • Performance tests for DNS Probe 0.5.0