Actions
Bug #6194
closed
Add 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.
Updated by François ARMAND almost 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/805
The PR is here: https://github.com/Normation/rudder/pull/805
Updated by François ARMAND almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 7b4f108283e999933cebd59aab67887a59ad60ae.
Updated by Nicolas CHARLES almost 10 years ago
Applied in changeset 9b61fd7175d586a2e3178a03f608f14288151ac0.
Updated by Vincent MEMBRÉ over 9 years ago
- Subject changed from Add a cach for compliance by node to Add a cache for compliance by node
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions