#414: Add --purge option for tuning memory usage#415
Merged
Conversation
Member
|
Can you add this functionality to the config file too? |
| ConstructLengths constructLengths = configuration.parseConstructLengths(); | ||
| Set<Rules> enabledRules = configuration.getEnabledRules(); | ||
|
|
||
| setNumberOfFilesBeforePurge(); |
Member
There was a problem hiding this comment.
I think this could be simplified to just numberOfFilesBeforePurge = configuration.numberOfFilesBeforePurge(); (no need to have a separate method for it) because that will default to 0, which will be semantically identical to not providing the --purge flag.
Member
|
👍 |
Member
|
👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #414 and adds a tuning mechanism to fix #325.