Project

General

Profile

Actions
Copy link

Bug #9864

closed

Bug #9854: Slow compliance computation in Rudder 4.0

getNodeStatusReports is called for each node, and is slow to compute PolicyMode Inconsistency

Added by Nicolas CHARLES almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
4.0.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

getNodeStatusReports is called for every nodes with new compliance, and it easily cost several seconds from a thousand of node

Issue is in computation of status, which iterate over all compliance, and is fairly expensive (even more with 9857 as it triggers actual compliance computation) - it represents 50 to 80% of the cost of this method

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #9869: Compliance on all reports is always computed, even when not necessaryReleasedVincent MEMBRÉActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 8 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/1411
Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 8 years ago

  • Status changed from Pending technical review to Rejected

Ticket #9869 fixed the root cause

Actions
Copy link
 #4

Updated by Nicolas CHARLES almost 8 years ago

  • Is duplicate of Bug #9869: Compliance on all reports is always computed, even when not necessary added
Actions
Copy link

Also available in: Atom PDF