Cool! :-)
Cheers,
Florin
> On Feb 19, 2018, at 9:03 AM, Ray Kinsella wrote:
>
> Insufficient hugepages in the VM - thanks for everyone's help!
>
>
> Ray K
>
> On 19/02/2018 15:38, Ray Kinsella wrote:
>> Part of the mystery is solved in any case,
>> Looks to be related to running inside the
Insufficient hugepages in the VM - thanks for everyone's help!
Ray K
On 19/02/2018 15:38, Ray Kinsella wrote:
Part of the mystery is solved in any case,
Looks to be related to running inside the VM.
DBGvpp# test tcp clients nclients 4 mbytes 256 test-timeout 100 uri
tcp://192.168.1.1/9000
Part of the mystery is solved in any case,
Looks to be related to running inside the VM.
DBGvpp# test tcp clients nclients 4 mbytes 256 test-timeout 100 uri
tcp://192.168.1.1/9000
4 three-way handshakes in 4.10 seconds .98/s
Test started at 10.538212
Test finished at 26.065026
1073741824 bytes
Hi Ray,
The only thing missing with memif is TCO but that shouldn’t be a reason for
such a drop. I noticed you’re running a debug image, could you try with release
as well?
Cheers,
Florin
> On Feb 14, 2018, at 7:42 AM, Ray Kinsella wrote:
>
>
> Hi Florin,
>
> So I connected the two contai
Hi Florin,
So I connected the two containers directly as Memif Master/Slave, taking
in VPP vSwitch completely out. Performance is double - but still is
pretty awful.
Could this be because I am not using DPDK under the hood in either
Container?
Ray K
DBGvpp# test tcp clients nclients 1 mb
It would really help if read the whole email!
Apparently the test finishes, albeit with miserable performance! So, for some
reason lots and lots of packets are lost and that’s what triggers the
“heuristic” in the test client that complains the connection is stuck. What
does “show error” say? Do
As a first step, show session verbose 2 on the two instances, to see where
we’re at.
Florin
> On Feb 13, 2018, at 8:20 AM, Ray Kinsella wrote:
>
> Still stuck ...
>
> DBGvpp# test tcp clients nclients 1 mbytes 16 test-timeout 100 uri
> tcp://192.168.1.1/9000
> 1 three-way handshakes in .05
Still stuck ...
DBGvpp# test tcp clients nclients 1 mbytes 16 test-timeout 100 uri
tcp://192.168.1.1/9000
1 three-way handshakes in .05 seconds 21.00/s
Test started at 205.983776
0: builtin_client_node_fn:216: stuck clients
Test finished at 229.687355
16777216 bytes (16 mbytes, 0 gbytes) in 23.
Hi Ray,
Interesting. What happens if you add: test-timeout 100 to the client cli?
Florin
> On Feb 13, 2018, at 7:35 AM, Ray Kinsella wrote:
>
> Hi folks,
>
> I am messing around trying to do some throughput testing with v18.01 VPP TCP
> and I keep ending up getting the error "stuck clients"
Hi folks,
I am messing around trying to do some throughput testing with v18.01 VPP
TCP and I keep ending up getting the error "stuck clients" for what
feels like a pretty modest setup.
* I am using two containers connected via a VPP vSwitch w/memif interfaces.
* In the default namespace I am
10 matches
Mail list logo
