Project

General

Profile

Actions

Bug #20316

closed

Compliance is cached as a whole for all node, but used as System and User compliance

Added by Nicolas CHARLES about 1 year ago. Updated about 1 year ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
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)


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #20318: Improve performance of getUserAndSystemNodeStatusReports by exploring only once cacheReleasedFran├žois ARMANDActions
Actions #1

Updated by Nicolas CHARLES about 1 year ago

  • Related to Bug #20318: Improve performance of getUserAndSystemNodeStatusReports by exploring only once cache added
Actions #2

Updated by Nicolas CHARLES about 1 year ago

  • Description updated (diff)
Actions #3

Updated by Nicolas CHARLES about 1 year ago

  • Status changed from New to Rejected

there are other ways to do that, like in related ticket
closing

Actions

Also available in: Atom PDF