-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run vBNG VNF/CNF tests and collect results #35
Comments
vBNG VNF Benchmarks
CPU pinning done on running VMs using Performance is currently limited by Pktgen, as each of the two ports only support 1 rx/tx queue, which limits the CPU usage to 2 cores. This limitation will be true for both VNF and CNF tests as both will use the same VM version of Pktgen. Once we figure out an alternative to the vhost-user interfaces (e.g. SR-IOV) it should be possible to increase the queues per port, which should increase the throughput and remove the bottleneck. |
vBNG CNF Benchmarks
The difference in throughput between VNF and CNF is negligible, as both are limited by the number of packets generated by the Pktgen VM Performance is currently limited by Pktgen, as each of the two ports only support 1 rx/tx queue, which limits the CPU usage to 2 cores. This limitation will be true for both VNF and CNF tests as both will use the same VM version of Pktgen. Once we figure out an alternative to the vhost-user interfaces (e.g. SR-IOV) it should be possible to increase the queues per port, which should increase the throughput and remove the bottleneck. |
This ticket can be closed |
Tasks:
The text was updated successfully, but these errors were encountered: