On Thu, Aug 31, 2017 at 09:48:14AM +0300, Liran Schour wrote:
> ovs-dev-boun...@openvswitch.org wrote on 30/08/2017 07:33:13 PM:
> > The current implementation of ovsdb-server caches only non-conditional
> > monitors, that is, monitors for every table row, not those that monitor
> > only rows that
ovs-dev-boun...@openvswitch.org wrote on 30/08/2017 07:33:13 PM:
> The current implementation of ovsdb-server caches only non-conditional
> monitors, that is, monitors for every table row, not those that monitor
> only rows that match some condition. To figure out which monitors are
> conditional,
On Wed, Aug 30, 2017 at 9:33 AM, Ben Pfaff wrote:
> The current implementation of ovsdb-server caches only non-conditional
> monitors, that is, monitors for every table row, not those that monitor
> only rows that match some condition. To figure out which monitors are
> conditional, the code trac
The current implementation of ovsdb-server caches only non-conditional
monitors, that is, monitors for every table row, not those that monitor
only rows that match some condition. To figure out which monitors are
conditional, the code track the number of tables that have conditions that
are unifor