Difference between revisions of "GoVPP/Performance"
From fd.io
< GoVPP
(Created page with " == GoVPP Performance == GoVPP performance has been measured using the [https://gerrit.fd.io/r/gitweb?p=govpp.git;a=blob;f=examples/cmd/perf-bench/perf-bench.go;h=e414b204fca...") |
(→GoVPP Performance) |
||
Line 4: | Line 4: | ||
GoVPP performance has been measured using the [https://gerrit.fd.io/r/gitweb?p=govpp.git;a=blob;f=examples/cmd/perf-bench/perf-bench.go;h=e414b204fcadfc9965ac231adce9f495145a8e05;hb=HEAD 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. | GoVPP performance has been measured using the [https://gerrit.fd.io/r/gitweb?p=govpp.git;a=blob;f=examples/cmd/perf-bench/perf-bench.go;h=e414b204fcadfc9965ac231adce9f495145a8e05;hb=HEAD 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: | + | 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: |
{| class="wikitable" | {| class="wikitable" | ||
Line 24: | Line 24: | ||
|GoVPP - interface dump | |GoVPP - interface dump | ||
|210 305 req/second | |210 305 req/second | ||
+ | |} | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |+Synchronous API | ||
+ | |- | ||
+ | |1 | ||
+ | |C application - control ping | ||
+ | |2340 req/second | ||
+ | |- | ||
+ | |2 | ||
+ | |GoVPP - control ping | ||
+ | |107req/second | ||
|} | |} |
Revision as of 14:40, 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 | 107req/second |