-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
rhel-virt-networking-core
-
ssg_virtualization
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
After we do some benchmark tests between VDUSE and VETH, we found some gaps, e.g., the TCP throughput for large packet size and latency.
So we need to analyse and optimize the performance to reduce the gap.
Here are detailed results:
Pod <-> Pod scenario
after the patch [#virtio-net: tweak for better TX performance in NAPI mode]https://web.git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/virtio_net.c?id=e13b6da7045f997e1a5a5efd61d40e63c4fc20e8
Pod <-> remote host scenario
after the patch [#virtio-net: tweak for better TX performance in NAPI mode]https://web.git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/virtio_net.c?id=e13b6da7045f997e1a5a5efd61d40e63c4fc20e8
- depends on
-
RHEL-84260 VDUSE performance comparions between TCP STREAM and TCP_SENDFILE
-
- Closed
-
-
RHEL-84262 VDUSE and VETH performance comparions on Pod <-> remote host
-
- Closed
-
-
RHEL-84266 VDUSE and VETH performance comparions with optimization patch on Pod <-> Pod
-
- Closed
-