Thanks Ben. Just to give a bit of background, we have a 32 cpu system. If i
bring up ovs using the default i see that ovs-vswitchd takes around 290 MB of
memory. Majority of this is coming from the stack size consumption for the
various threads.If i restrict the other-config:n-handler-threads and
other-config:n-revalidator-threads to 1, i see the rss of ovs-vswitchd comes
down to 40MB.
I am looking to see if the extra ~= 250 MB is really needed for my case where i
would not have any flow rules in the user space and i would be using ovs as a
plain L2 switch. I would be having 3-4 ovs bridges though at the max.
truly, Srinivas.
On Saturday, 20 October, 2018, 4:27:05 AM IST, Ben Pfaff <[email protected]>
wrote:
On Fri, Oct 19, 2018 at 07:26:14PM +0000, Srinivas via discuss wrote:
> Hello all,We are starting with ovs and want to use it as
> a) a L2 switch with vlan tagging on the guest vm ports.b) no openflow rules
> will be configured.c) We will have 4 -5 bridges created on the system with
> each bridge having a corresponding bond interface along with the guest
> vtap's.
> Given the above, how do we tune ovs-vsctl parameters.?Does each bridge
> correspond to a data path? If so what should we set the
> other-config:n-handler-threads and other-config:n-revalidator-threads to?
>
> We want to make sure the ovs-vswitchd starts off with the right number of
> threads.
We try to make OVS have good defaults, so that it isn't necessary to do
this kind of configuration at all. I recommend testing the performance
before considering any tuning.
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
