... | ... | @@ -13,8 +13,7 @@ DNS Probe was run with default Sysrepo configuration with only `export-format` c |
|
|
|
|
|
## 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.
|
|
|
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 |
|
|
|
|----------------------------------------------------------|---|---|---|
|
... | ... | @@ -23,10 +22,11 @@ different configurations depending on the packet processing backend and export f |
|
|
| AF\_PACKET - Parquet | 487 000 | 780 000 | 1 350 000 |
|
|
|
| AF\_PACKET - C-DNS | 805 000 | 1 242 000 | 2 017 000 |
|
|
|
|
|
|
The following graph summarizes the results. It can be seen that performance scales linearly with the number of packet processing threads in all four combinations of backend and output format.
|
|
|
|
|
|
![DNS Probe performance](figures/perf.svg "DNS Probe performance")
|
|
|
|
|
|
For comparison [*dnscap*](https://www.dns-oarc.net/tools/dnscap) and [*netsniff-ng*](http://netsniff-ng.org/)
|
|
|
utilities for capturing DNS traffic to PCAPs were tested on the same data set.
|
|
|
For a baseline comparison, [*dnscap*](https://www.dns-oarc.net/tools/dnscap) and [*netsniff-ng*](http://netsniff-ng.org/) utilities for capturing DNS traffic to PCAPs were tested on the same data set. It has to be noted that this comparison is not entirely fair because DNS Probe performs more packet processing and also matches the corresponding DNS queries and responses.
|
|
|
|
|
|
| Utility (pkts/s) / Packet processing threads | 1 | 2 | 4 |
|
|
|
|----------------------------------------------|---|---|---|
|
... | ... | |