Actions
Bug #24047
closedCompliance has unoptimized usage of map view and policy mode computation
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:
To do
Regression:
No
Description
In node group and node compliance, getting the policy mode re-computes some computation that is done earlier: getting node ids for a rule.
Some collection operations on node facts are also slow are they are re-computed every time instead of being stored in-memory
Updated by Clark ANDRIANASOLO 9 months ago
- Related to User story #23935: API for node group compliance added
- Related to Bug #24028: Add policy mode info in group compliance details added
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5334
Updated by Clark ANDRIANASOLO 9 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|a7536a8d3cdc061f1dcbd892a74ab91760bbc9d6.
Updated by Vincent MEMBRÉ 6 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.0~beta1 which was released today.
Actions