Open Stack

For high CPU usage for openvswitchd there is a simple solution: upgrade 
to anything like 1.11 or higher. There is a huge problem with ovs 1.4, 
1.9, 1.10 - they suck at real-world network activity. All new version 
(2.0, 2.1) are much better and works great.

You can find more detail in google with keyword 'megaflow ovs'.

On 09/30/2014 05:34 PM, Robert van Leeuwen wrote:
> Hi,
>
> Just wondering:
> Did anyone do a migration from ovs to linuxbridge?
>
> We are considering this due to reducing complexity and improving performance:
> - Fewer moving parts = less that can go wrong
> - We have hypervisores with the ovs eating a significant amount of cpu cycles (more than one cpu core)
>
> However, it seems that there is more to it then just changing the config on the hypervisors and (hard) rebooting the instances.
>  From what I have gathered there is stuff saved in the databases:
> * neutron - ml2_port_bindings - This seems to be easily updated with some SQL statements.
> * nova - instance_info_caches - This looks like it is going to be a problem, the whole network stuff is in here.
> Although it is called cache it does not seem to be updated if you delete the content :(
>
> Anyone tried this before? :)
>
> Cheers,
> Robert van Leeuwen
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators