On Dec 2, 2017 3:18 PM, "Roman Bolshakov" <roolebo@gmail.com> wrote:
Hi Yaniv,

It wouldn't be an issue if all actions (create an external network, import it and assign to some oVirt clusters) would take less than a second. I don't know if it's possible in oVirt 4.1.x or 4.2.x. When oVirt is used in CI to provision VMs, every second matters.

Interesting. I would have thought other bottlenecks, such as storage performance, might be an issue. 


OVN itself can create new logical switch in 16ms, when it has a thousand of logical switches. It can also be queried very fast as OVSDB protocol allows to request only one network.

I doubt we'll come remotely close to this. The overhead of the whole communication path won't allow oVirt to come close to that, but we'll look at it. 
Y. 


Thanks,
Roman

сб, 2 дек. 2017 г. в 9:55, Yaniv Kaul <ykaul@redhat.com>:


On Dec 1, 2017 6:59 PM, "Roman Bolshakov" <roolebo@gmail.com> wrote:
Hi,

We're using for OVN provider for half a year and noticed a few performance issues when networks are created programmatically:

1. Network listing on external provider takes around a second with ~1000 OVN networks on bare oVirt cluster (engine + 2 hosts) with no VMs

That's an issue? 1s for 1000 networks looks OK to me. 

2. Network import from external provider takes around 1,6 second on the cluster

Same? 
Y. 

3. External network provider API doesn't allow to query specific network by name.
4. System networks don't have external id field. Without it we need to list all external networks to delete one, which is slow due to #3.

In the end, we get a few seconds to delete/create an external network end-to-end.

We're using oVirt 4.1.7. Which of the issues are going to be fixed in 4.2?

Thanks,
Roman

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users