Actions
Bug #20316
closed
Compliance is cached as a whole for all node, but used as System and User compliance
Status:
Rejected
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:
Description
The compliance is cached o for each node, but for all rules applied (system & user)
So when we query it, we (nearly) always need to split it in two in getUserAndSystemNodeStatusReports, and look at compliance for user and compliance of system rules
this is done be recreating 2 new NodeStatusReport, one for each state
this is not overly complex, but this causes new objects to be created for nothing, and is a bit expensive (350ms * 2for 10 000 nodes)
Updated by Nicolas CHARLES about 3 years ago
- Related to Bug #20318: Improve performance of getUserAndSystemNodeStatusReports by exploring only once cache added
Updated by Nicolas CHARLES about 3 years ago
- Status changed from New to Rejected
there are other ways to do that, like in related ticket
closing
Actions