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.
What:
Speed up result counting iterator.
2 parts:
Test case was an
--optimize rebuild-report-cache
that took 32s on master.With 1 the test case dropped to 23s, with 1 and 2 it dropped to under 4s.
Why:
Immediate problem: Result counting slows down the report upload used to generate big dbs.
How did you test it:
time gvmd --optimize rebuild-report-cache
on master (32s)psql gvmd -c "SELECT report, user, severity, count, override, end_time, min_qod from report_counts;" > /tmp/rc_master
time gvmd --optimize rebuild-report-cache
with patch (4s)psql gvmd -c "SELECT report, user, severity, count, override, end_time, min_qod from report_counts;" | sort > /tmp/rc_pr
sort /tmp/rc_master | diff - /tmp/rc_pr
(same)Checklist: