Actions
Bug #9864
closed
Bug #9854: Slow compliance computation in Rudder 4.0
getNodeStatusReports is called for each node, and is slow to compute PolicyMode Inconsistency
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
getNodeStatusReports is called for every nodes with new compliance, and it easily cost several seconds from a thousand of node
Issue is in computation of status, which iterate over all compliance, and is fairly expensive (even more with 9857 as it triggers actual compliance computation) - it represents 50 to 80% of the cost of this method
Updated by
Actions