Hi Han,

On 17.03.2017 23:36, Han Zhou wrote:

On Fri, Mar 17, 2017 at 2:50 AM, Valentine Sinitsyn
<[email protected] <mailto:[email protected]>> wrote:
Did you restart controllers or ovn-northd after running full tests
before binding more ports. It would be interesting to learn how long
does it take warm up IDL in controllers/northd in your setup.

No need to restart. It will cool down when test ends. On top of the
scale, we can just test creating & binding 500 lports and then tear down
the 500 lports before next test, which takes much less time than the
full run from empty.


Moreover, in current ovs-scale-test code, the step "wait 100 lport up"
is updated utilizing a new feature (wait for HVs to catch up) that was

Are you referring to ovn-nbctl --wait-until, or something else? If you
were not using it for the talk, what exactly does "create + bind" mean
on the graph?

--wait-until has been used always, to wait lport state become "up" in
NB, which means port binding is reflected in NB. The new change [1] was
using the new feature of ovn-nbctl: "sync --wait=hv" which will wait
until the port binding to be processed on all HVs. This feature was not
there yet when we had the talk, and no reasonable alternative to achieve
the same.
Got you know. This may affect the test negatovely indeed, as OVSDB seems to scale poorly with the number of clients, as our tests suggest.

Thanks you again.

Valentine

[1]
https://github.com/openvswitch/ovn-scale-test/commit/0ece1038de45f05f461b45162b21a8bde2793010
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to