Difference between revisions of "GoVPP/Performance"
From fd.io
< GoVPP
(→GoVPP Performance) |
(→GoVPP Performance) |
||
| Line 35: | Line 35: | ||
|2 | |2 | ||
|GoVPP - control ping | |GoVPP - control ping | ||
| − | | | + | |107 req/second |
|} | |} | ||
Revision as of 14:44, 11 July 2017
GoVPP Performance
GoVPP performance has been measured using the perf-bench example binary on an Ubuntu 16.04 LTS virtual machine running on a laptop with Intel® Core™ i7-6820HQ CPU @ 2.70GHz and 16 GB of RAM. The virtual machine has been assigned all CPU cores and 8 GB of RAM.
The benchmark application is able to measure the performance of both synchronous and asynchronous binary API. As the results of the benchmark show; in case that speed is an issue, asynchronous API is recommended:
| 1 | C application - control ping | 762 000 req/second |
| 2 | GoVPP - control ping | 251 878 req/second |
| 3 | GoVPP - l2fib add | 245 560 req/second |
| 4 | GoVPP - interface dump | 210 305 req/second |
| 1 | C application - control ping | 2340 req/second |
| 2 | GoVPP - control ping | 107 req/second |
