transactions cause new DB connections (no pooling in use)
Bug #140817 reported by
Christian Reis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Stuart Bishop | ||
Bug Description
In the process of debugging the test suite this week, Francis and I established that the librarian daemon ends up reconnecting for every single _getFileAlias() call the client issues. The reason is that _getFileAlias() issues a begin() and a commit(), and this causes the connection handling code in sqlbase.py to obtain new connections.
Ideally, we should reuse connections, at least in the librarian daemon. The overhead of reconnecting for every single file fetch is too high.
Revision history for this message
| Christian Reis (kiko) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → flacoste |
| importance: | Undecided → Medium |
Revision history for this message
| Christian Reis (kiko) wrote | #2 |
| Changed in launchpad: | |
| status: | New → Confirmed |
| Changed in launchpad-foundations: | |
| assignee: | flacoste → nobody |
| status: | Confirmed → Triaged |
Revision history for this message
| Robert Collins (lifeless) wrote | #3 |
| summary: |
- The librarian reconnects too often (and takes too long to do so) + transactions cause new DB connections (no pooling in use) |
| Changed in launchpad-foundations: | |
| assignee: | nobody → Stuart Bishop (stub) |
| Changed in launchpad-foundations: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This may be the source of some of the slowness in the test suite.