On Thu, Mar 10, 2016 at 05:20:06PM -0800, Han Zhou wrote: > On Thu, Mar 10, 2016 at 4:01 PM, Ben Pfaff <[email protected]> wrote: > > > > Beyond supporting this usage model, the basic requirements for the OVN > > use case are: > > > > - Size: 20 MB to 100 MB of data (estimated database size to hold > > data for our target scale of 1,000 hypervisors and 20,000 > > logical ports). > > > > - Scale: The northbound database has only a single-digit number of > > clients. Each hypervisor is a client to the southbound > > database, so about 1,000 clients for our target scale of 1,000 > > hypervisors. > > > > Ben, is there any reason we limit the scale to 1,000 hypervisors? OVN seems > have much more potential than that based on current tests, even with ovsdb. > As for ports, considering container use cases, there can be more than > 20,000 even for 1,000 hypervisors.
I have been considering this as a minimum interesting scale. It's hard for me to know what the interesting scale range is. I am really happy to hear what is important to you? Can you tell me about what you want to scale to? > > - OVSDB. If we choose to use OVSDB, we'll have to add > > high-availability support. Also, the table doesn't mention > > scaling, since it's hard to compare objectively, but the OVSDB > > server currently doesn't scale well to the 1000 clients required > > for the southbound database, although Andy has started working > > on that. > > That's not true :). With probe disabled, in our scale testing OVSDB server > is not yet the bottleneck with 1000 clients connected to southbound DB. Wow. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
