Actions
Bug #20318
closed
Improve performance of getUserAndSystemNodeStatusReports by exploring only once cache
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
we are calling twice findRuleNodeStatusReports, so we waste time by exploring twice the cache
https://issues.rudder.io/issues/20316
this has a peculiar impact in 7.0 where the API is used for node list
Updated by Nicolas CHARLES about 3 years ago
- Related to Bug #20316: Compliance is cached as a whole for all node, but used as System and User compliance added
Updated by Nicolas CHARLES about 3 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES about 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4018
Updated by Nicolas CHARLES about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|2a4209b29004439169aec723af7e1beb21565636.
Updated by Nicolas CHARLES about 3 years ago
Applied in changeset rudder|0098fd30ee5f415eb1677cb959c77f29896f5c0d.
Updated by François ARMAND about 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.2.12 and 7.0.0~rc2 which were released today.
Actions