Project

General

Profile

Actions
Copy link

Bug #16643

closed

Unecessary compliance computations when historization of Node Compliance is disabled

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

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

Description

We can disable serialization of node compliance and node compliance level to save ressource
However, disabling them does not save that much ressource: compliance is still recomputed, and then discarded

we ought to do better than that

Actions
Copy link

Also available in: Atom PDF