Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Transaction pruning improvments #7183
Conversation
mjs
added some commits
Mar 31, 2017
|
$$merge$$ |
|
Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju |
jujubot
merged commit 42c12c8
into
juju:develop
Mar 31, 2017
mjs
deleted the
mjs:1676427-txn-pruning
branch
Mar 31, 2017
| - // Prune txns only when txn count has doubled since last prune. | ||
| - return runner.MaybePruneTransactions(2.0) | ||
| + // Prune txns when txn count has increased by 10% since last prune. | ||
| + return runner.MaybePruneTransactions(1.1) |
jameinel
Mar 31, 2017
Owner
I do wonder if we could have some sort of an absolute threshold as well. "Prune if transactions have grown by 1M regardless of the % increase".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mjs commentedMar 31, 2017
Description of change
Two parts:
Update to newest juju/txn to pull in the improved txn pruning algorithm.
Prune transactions after 10% growth. Previously we would only prune after 2x growth which wasn't aggressive enough and made the prune process impact system resources much more
when it did run. Now that the pruning process is much more efficient running it more often is ok.
QA steps
Documentation changes
N.A. (internal only)
Bug reference
https://bugs.launchpad.net/juju/+bug/1676427