Actions
Bug #6194
closedAdd a cache for compliance by node
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
Node compliance takes a long time to compute (several seconds for ~1000 nodes).
And we exactly when they are updated: either on configuration modification, or when a new run comes.
So it's easy to build a cache and know when to invalidate it;
So let's do it and make Rudder fast.
Actions