++profile++sqltrace can take so long to calculate that it is unusable as a diagnostic on qastaging and staging in some cases
Bug #838878 reported by
Gary Poster
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Gary Poster | ||
Bug Description
Generating tracebacks is expensive. We ought to be able to selectively choose which SQL statements get a traceback.
Related branches
lp:~gary/launchpad/bug838878
- j.c.sackett (community): Approve
-
Diff: 913 lines (+430/-117)3 files modifiedlib/lp/services/profile/profile.pt (+121/-36)
lib/lp/services/profile/profile.py (+153/-53)
lib/lp/services/profile/tests.py (+156/-28)
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r13858 <http://