You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Opencontrail vrouter R3.2 branch and build the dpdk vrouter rpm.
however, we compared the performance between kernel-vrouter and dpdk-vrouter, found that, kernel-vrouter has 6.XG bandwidth, but the dpdk-vrouter only have 4.XG bandwidth. But dpdk-vrouter's PPS is better than kernel-vrouter, which is same as your mentioned in some contrail vrouter documents.
test path is
vm1--->vrouter in host1--->host1 NIC ---> host2 NIC ---> vrouter in host2 --->vm2
physical bandwidth of NIC is 10G
host1 and host2 is numa framework.
we set hugepages to 1G, and kvm use mem-path to use hugepages
could you pls tell me whether the performance is influenced when we use memory in different numa node, and when NIC and CPU cores pinned to dpdk-vrouter is in different numa node?
could you pls give me some advices what may affect this performance? how to improve dpdk-vrouter performance?
any suggestions and advices will be appreciated!
The text was updated successfully, but these errors were encountered:
We are using Opencontrail vrouter R3.2 branch and build the dpdk vrouter rpm.
however, we compared the performance between kernel-vrouter and dpdk-vrouter, found that, kernel-vrouter has 6.XG bandwidth, but the dpdk-vrouter only have 4.XG bandwidth. But dpdk-vrouter's PPS is better than kernel-vrouter, which is same as your mentioned in some contrail vrouter documents.
vm1--->vrouter in host1--->host1 NIC ---> host2 NIC ---> vrouter in host2 --->vm2
could you pls tell me whether the performance is influenced when we use memory in different numa node, and when NIC and CPU cores pinned to dpdk-vrouter is in different numa node?
could you pls give me some advices what may affect this performance? how to improve dpdk-vrouter performance?
any suggestions and advices will be appreciated!
The text was updated successfully, but these errors were encountered: