ROX-31176: improve reprocess deployment risk#17126
Conversation
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
dashrews78
left a comment
There was a problem hiding this comment.
Awesome. Please update the description to refer to the correct method though as this doesn't apply to SearchRawProcessIndicators.
|
Images are ready for the commit at 1857c3b. To use with deploy scripts, first |
|
Indeed awesome! |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #17126 +/- ##
=======================================
Coverage 48.76% 48.76%
=======================================
Files 2712 2712
Lines 202430 202443 +13
=======================================
+ Hits 98720 98729 +9
- Misses 95931 95935 +4
Partials 7779 7779
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
The current
GetProcessIndicatorsRiskViewcalls are inefficient for our use case, since we need to loop through the returned process indicators. Switching to a callback-based approach allows us to process items one by one, avoiding the need to load all objects into a slice. This reduces memory usage and lowers GC pressure.go test -tags sql_integration -run=NO -bench=BenchmarkEvaluateBaselinesAndPersistResult ./central/processbaseline/evaluator/. -count 6 -benchmem -benchtime 3srefs: