It's hard to debug DB performance issues without configured profiler

Bug #1817605 reported by Pavel
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description
When I was trying to undestand why I have the issue described at the link above, I noticed that it was pretty complicated to identify source of the problem. I believe that debug mode is a good place to expose time consumed by DB calls. I implemented a small fix for this and whill push it shortly.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on senlin (master)

Change abandoned by "Erik Olof Gunnar Andersson <email address hidden>" on branch: master

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.