Bug #20316
Updated by Nicolas CHARLES over 2 years ago
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) nothing