🐛 Back-port 0.3: Reaper optimization. #698
Open
+138
−143
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.
The default reaper frequency is (1) minute.
The reapers are performing 3-4 queries for every file and bucket evaluated for reaping. With the addition of attaching files to tasks and task-reports, the number of files has increased substantially. The current algorithm will run 3-4 queries for each resource evaluated.
For example: A deployment with 2000 analyzed applications can have ~25,000 files. To evaluate 4 resources for references (Task, TaskGroup, Rule, Target) resulted in 100,000 queries each reaper run.
This PR each run (default: 1/ minute) :