Merge lp:~jameinel/launchpad/loggerhead-clear-cache into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | John A Meinel on 2012-08-16 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 15819 |
| Proposed branch: | lp:~jameinel/launchpad/loggerhead-clear-cache |
| Merge into: | lp:launchpad |
| Diff against target: |
16 lines (+6/-0) 1 file modified
lib/launchpad_loggerhead/app.py (+6/-0) |
| To merge this branch: | bzr merge lp:~jameinel/launchpad/loggerhead-clear-cache |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Robert Collins (community) | 2012-08-15 | Approve on 2012-08-15 | |
|
Review via email:
|
|||
Commit Message
When loggerhead finished with a branch, have it clear its caches, rather than waiting for the GC to do so.
Description of the Change
This is a small tweak for the Launchpad Loggerhead app that drive bazaar.
Specifically, every request to loggerhead gets a new bzrlib.
So this is just helping things along. Once we've finished an HTTP request, directly request that caches at least get cleared out.
In doing a test of just spidering of the launchpad codebase using bazaar.
A different option would be to look into changing how branches are opened, and possibly caching them. It would theoretically help performance a lot, we wouldn't be re-reading all the same content over and over. However at this point, I'd rather drop a cache than add a new one.
