checkwatches doing an unreasonable amouht of db work
Bug #435952 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
checkwatches is noticeably one of the higher consumers of database resources, often chewing up 30-70% of a core all on its own. This seems unreasonable given its job, and may indicate a sily bug or badly thought out piece of code.
I suspect something like:
- missing join condition
- unnecessary repetition of queries
- suboptimal queries
- retrieving lots of rows one row at a time
We should instrument it and work out wtf it is spending its time. LP_DEBUG_SQL or LP_DEBUG_SQL_EXTRA might provide enough information if we summarize it.
It it does need to do this much work, we should probably try and offload some or most of it to a slave database.
Changed in malone: | |
assignee: | Graham Binns (gmb) → nobody |
Changed in malone: | |
importance: | Critical → Medium |
tags: | added: story-reliable-bug-syncing |
Changed in malone: | |
importance: | Medium → High |
tags: | added: canonical-losa-lp |
To post a comment you must log in.
Assigning to gmb because he said he would take a look.
This isn't a major production concern... yet ;)