Hui Kang/Watson/IBM wrote on 06/25/2016 07:53:36 PM:
> From: Hui Kang/Watson/IBM
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: Ben Pfaff <b...@ovn.org>, dev@openvswitch.org
> Date: 06/25/2016 07:53 PM
> Subject: Re: [ovs-dev] [OVN] Potential scalability bug in ovn-northd
> on creating and binding large number of lports
>
> > >
> > > Actually, I take that back. The cycles/port for all the cases above
> > > demonstrate only slightly nonlinear scaling: 200/25 is 8
Mcycles/port,
> > > 1200/125 is 9.6 Mcycles/port.
> > >
> > > So the issue is not that it does not scale. The issue is that it is
> > > slow.
> >
> > Er? When I do the ratios, I come up with 125 Kcycles/port at 200 ports
going
> > down to slightly more than 104 Kcycles/port at 1200 ports, which is
slightly
> > sub-linear (and I do think that's a good thing).
> >
> > However, I'm left wondering if it would be possible to make things even
> > better through judicial use of persistence and incremental processing.
> >
> > Right now the ports logic looks to me like:
> > - Build a list of all ports known via port bindings in the sb db.
> > - For each port known via the nb db:
> > - Look for the port in the sb list.
> > - If found, move the port from the sb list to the both list
> > - If not found, create a new entry in the nb_only list.
> > (After the above finishes, we have three lists: sb_only, nb_only, and
both)
> > - For each entry in the both list, do modifications to align the port
> > binding with nb information.
> > - For each entry in the nb_only list, create port_binding information
in
> > the sb db.
> > [If I were updating the port lists, I'd move the port from the
nb_only
> > list to both list]
> > - For each entry in the sb_only list, remove from the port_binding
table.
> > [If I were updating the sb_only list, I'd remove it from the sb_only
> > list]
>
> Hi, Ryan
> Thanks for drafting the pseudo-code.
> Please allow me to add number bullets in your original version to
accommodate
> further discussions.
That's fine, I updated from sb list to sb_only to be more clear as well
>
> 1. Build a list of all ports known via port bindings in the sb_only db.
> 2. For each port known via the nb db:
> 2.1 Look for the port in the sb_only list.
> 2.2 If found, move the port from the sb_only list to the both list
> 2.3 If not found, create a new entry in the nb_only list.
> (After the above finishes, we have three lists: sb_only, nb_only, and
both)
> 3. For each entry in the both list, do modifications to align the port
> binding with nb information.
> 4. For each entry in the nb_only list, create port_binding information in
> the sb db.
> [If I were updating the port lists, I'd move the port from the nb_only
> list to both list]
> 5. For each entry in the sb_only list, remove from the port_binding
table.
> [If I were updating the sb_only list, I'd remove it from the sb_only
> list]
>
> In square bracket of step 4., do you mean "If I were updating the
nb_lists in
> step 2.3., ..."?
No, that is part of the "if I were going to persist all the port lists,
what would I need to do"
> Similarly, in step 5, do you mean "If I were updating the sb_only list in
> step 2.2,..."?
Ditto the above explanation.
> In my opinion, step 4 and step 5 could be avoided with your logic in
square
> bracket. Is my understanding correct?
No, as those both still need to be performed whether I persist the port
lists
in ovn-northd or not.
> >
> > I *think* if I were to consider persisting the sb_only, nb_only, and
both
> > lists and follow the extra logic I've added in square brackets above,
I'd
> > only have entries in the both list at the end of the calculation set,
so I
> > should only need to persist the both table.
>
> What do you mean by "persisting"? A global linked list to store the
elements
> of struct ovn_ports?
That's exactly what I mean. I'm looking at trading memory for execution
time.
> > Further, I *think* if I were to then apply change tracking to the first
> > part of the process above, the logic changes to:
>
> Which step of the above pseudo-code should the following code be
> embedded into ?
The following replaces the entire list above. The good thing about writing
this down is that I can come back to it later and realize where I goofed -
see below.
> >
> > - For each tracked entry in the port bindings table
> > - if it is a deleted entry, remove from the both list (if there is
still
> > a nb entry, we'll recreate it further on)
> > - if it is a new entry, add it to the sb_only list
The above isn't quite right - since we create port binding entries ourself
in response to unmatched ports in the nb_only list, we need to check that
there isn't already a port in the both list. So the above changes to:
- if it is a new entry, check for it in the both list
- if it is not there, then add it to the sb_only list
> > - if it is a modified entry, find it in the both list and update the
> > sb information contained in the entry
> > - For each port known via the nb db:
> > - if the entry is found in the both list, update the nb data
contained
> > in the entry
> > - if the entry is not in the both list, but is in the sb_only list,
> > move the entry from the sb_list to the both list
> > - if the entry is not in either the both or the sb_only list, create
> > a new entry in the nb_only list
> > - For each entry in the both list, do modifications to align the port
> > binding with nb information.
> > - For each entry in the nb_only list, create port_binding information
in
> > the sb db and move the entry from the nb_only to the both list
> > - For each entry in the sb_only list, remove from the port_binding
table.
> >
> > Now, I'm pretty sure this will cut down the number of cycles, but
before
> > I go off and code it [and potentially break something ala yesterday's
> > excitement], I'm looking for some verification of both my conclusion of
> > persisting just the both list and the modified logic incorporating the
> > persisted both list and port binding change tracking adjustments). Do
> > these make sense or have I missed something?
Ryan
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
