Hi Edouard,
When a new flow is created, the first packet of the flow is sent to the
vrouter agent to lookup policy. While the flow is for the agent to resolve it,
it is marked as a "HOLD" flow.
Vrouter limits the number of such flows to 4096. Packets for any new flows are
dropped by vrouter (and the "Flow Unusable" counter is incremented) when this
limit has been crossed.
This should be an ephemeral condition and new flows will be created once the
agent has resolved the older flows.
Raja
From: Dev
<[email protected]<mailto:[email protected]>>
on behalf of Édouard Thuleau
<[email protected]<mailto:[email protected]>>
Date: Wednesday, October 14, 2015 at 9:42 AM
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: [opencontrail-dev] Flow unsusable over new 1000req/s
Hi,
I'm doing some network stress tests on Contrail.
One of them is to measure at which rate a vrouter can create new ephemeral TCP
sessions.
To do that test, I'm using a tsung generator distributed on different VM (five)
and a nginx server that simply return an HTTP 204 code. I setted a floating IP
on the nginx server and tsung clients use it as HTTP endpoint. I also had to
tune some system and nginx parameters.
On the Contrail side, I just tested it on 1.10 branch for the moment. The
kernel module is loaded with 'vr_flow_entries' setted to 2097152 and the
vrouter agent 'FLOWS.max_vm_flows' to 20%.
The result is the vrouter starts to drop flow with reason "Flow Unusable" when
the tsung client try to send 1000 HTTP requests per seconds.
Do you think my results are correct? Do you see any mistake in my test bed?
Someone already tried that type of test? If yes, what's your results?
Regards,
Édouard.
_______________________________________________
Dev mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
