Actions
Bug #8195
closed
Bug #7735: OOM in Rudder when there are too many repaired reports
Correct memory profile and efficiency of non-compliant-reports logger
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
As defined in the parent task #7735, some of the OOM are not due to the repaired report cache, but to the code that logs error rerports.
This ticket address that subpart which is quite self-contained.
The process is a batch, so the optimisation are easy (main idea: cut a big batch in lots of little ones)
Updated by 
Updated by
Actions