Public bug reported:
On a large OVN DB, frozen_row() calls for the event notification
processing can add 10ms up to 40ms or more depending on the size of the
row (as compared to 4usec for just passing the Row object). This can
easily make startup times w/ large DBs increase by a factor of 3 or
more.
We are currently calling frozen_row() for every event, but we really
only need it for the events that we have registered.
** Affects: neutron
Importance: Undecided
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2011590
Title:
Startup times for large OVN dbs is greatly increased by frozen_row()
calls
Status in neutron:
In Progress
Bug description:
On a large OVN DB, frozen_row() calls for the event notification
processing can add 10ms up to 40ms or more depending on the size of
the row (as compared to 4usec for just passing the Row object). This
can easily make startup times w/ large DBs increase by a factor of 3
or more.
We are currently calling frozen_row() for every event, but we really
only need it for the events that we have registered.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2011590/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
