On 11/25/22 13:37, Ilya Maximets wrote: > OVSDB creates a separate object for each weak reference in order to > track them and there could be a significant amount of these objects > in the database. > > We also had problems with number of these objects growing out of > bounds recently. So, adding them to a memory report seems to be > a good thing. > > Counting them globally to cover all the copied instances in transactions > and the transaction history (even though there should be none). > It's also hard to count them per-database, because weak references > are stored on destination rows and can be destroyed either while > destroying the destination row or while removing the reference from > the source row. Also, not all the involved functions have direct > access to the database object. So, there is no single clear place > where counters should be updated. > > Signed-off-by: Ilya Maximets <[email protected]> > ---
Acked-by: Dumitru Ceara <[email protected]> Thanks, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
