Thank you Hau
i tested w iperf got similar results. I cannot find iperf2. Anyway ns to ns
directly without vpp is perfect 50 gbps throughput and 10us latency. Tested
w iperf3. This is very bothering since we decided to go w vpp instead of
ovs
Thanks in advance
-Sara
בתאריך 6 במרץ 2018 20:00, "Hao Fu (haof)" <h...@cisco.com> כתב:
I encountered the similar issue before. Try replacing iperf3 with iperf2.
Hao
On 3/6/18, 8:34 AM, "vpp-dev@lists.fd.io on behalf of Sara Gittlin" <
vpp-dev@lists.fd.io on behalf of sara.gitt...@gmail.com> wrote:
Also the throughput is very poor - iperf3 TCP ~ 2Mbps
what is wrong here ?
On Tue, Mar 6, 2018 at 6:20 PM, Sara Gittlin <sara.gitt...@gmail.com>
wrote:
> Hi,
> i have 2 namespaces connected with veth-pairs to vpp - see setup here
> [https://wiki.fd.io/view/VPP/Configure_VPP_As_A_Router_
Between_Namespaces]
>
> i see very big latency ~10ms when i ping between the 2 namespaces
> i expected to see latency in the order of 10's us
> -----------------------------------
> 4 bytes from 172.16.2.2: icmp_seq=1005 ttl=63 time=11.5 ms
> 64 bytes from 172.16.2.2: icmp_seq=1006 ttl=63 time=9.60 ms
> 64 bytes from 172.16.2.2: icmp_seq=1007 ttl=63 time=7.55 ms
> 64 bytes from 172.16.2.2: icmp_seq=1008 ttl=63 time=5.52 ms
> 64 bytes from 172.16.2.2: icmp_seq=1009 ttl=63 time=9.60 ms
> 64 bytes from 172.16.2.2: icmp_seq=1010 ttl=63 time=17.6 ms
> 64 bytes from 172.16.2.2: icmp_seq=1011 ttl=63 time=15.5 ms
> 64 bytes from 172.16.2.2: icmp_seq=1012 ttl=63 time=13.6 ms
> 64 bytes from 172.16.2.2: icmp_seq=1013 ttl=63 time=11.6 ms
> 64 bytes from 172.16.2.2: icmp_seq=1014 ttl=63 time=9.54 ms
> 64 bytes from 172.16.2.2: icmp_seq=1015 ttl=63 time=7.67 ms
> 64 bytes from 172.16.2.2: icmp_seq=1016 ttl=63 time=5.56 ms
> 64 bytes from 172.16.2.2: icmp_seq=1017 ttl=63 time=3.44 ms
>
> ------------------------------------
>
> Who can assist ?
>
> Thanks in advance
> -Sara
>
>
>
