Merge lp:~jtv/launchpad/message-sharing-rearrange-commits into lp:launchpad
Proposed by
Jeroen T. Vermeulen
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Jeroen T. Vermeulen | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | not available | ||||
Proposed branch: | lp:~jtv/launchpad/message-sharing-rearrange-commits | ||||
Merge into: | lp:launchpad | ||||
Diff against target: |
27 lines (+0/-10) 1 file modified
lib/lp/translations/scripts/message_sharing_migration.py (+0/-10) |
||||
To merge this branch: | bzr merge lp:~jtv/launchpad/message-sharing-rearrange-commits | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Bishop (community) | Approve | ||
Review via email: mp+14342@code.launchpad.net |
To post a comment you must log in.
= Rearranging gc and commits in message-sharing migration =
Memory usage is still an issue in the message-sharing migration script. It commits and gc's periodically, but in phase 3 we still see increasing object counts.
This script is a minor tweak to give us better debug output: it makes the explicit garbage-collection runs happen just after a commit, when there's an absolute minimum number of objects still pinned in memory by the ongoing transaction.
There's no functional impact, but the change makes sense even outside the debugging context because it's... well, it's... uh, it's just better.
No lint, no tests (well, run {{{bin/test -vv -t message.sharing}}} if you feel like it) and no miracle cures for this one.
Jeroen