ovsdb design


Dayavanti Gopal Kamath <dayavanti.gopal.kamath@...>
 

Hi sam, vishal,

Can we please reserve some time to discuss ovsdb design tomorrow?  like to discuss a few alternatives for –

1.       Single queue mechanism for both config and event processing

2.       Use of a single long running transaction chain causing huge heap allocations

3.       Full serialization via the single queue, vs using node id based serialization.

 

Thanks,

daya


Sam Hague
 



On Mon, Jul 23, 2018 at 11:56 AM Dayavanti Gopal Kamath <dayavanti.gopal.kamath@...> wrote:

Hi sam, vishal,

Can we please reserve some time to discuss ovsdb design tomorrow?  like to discuss a few alternatives for –

Yes, this a is a good topic so will add to the agenda.  

1.       Single queue mechanism for both config and event processing

2.       Use of a single long running transaction chain causing huge heap allocations

3.       Full serialization via the single queue, vs using node id based serialization.

 

Thanks,

daya

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev@...
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev