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
 #1

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #2

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

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #5

Updated by François ARMAND almost 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #6

Updated by Nicolas CHARLES almost 5 years ago

  • Subject changed from Lots and lots of unecessary compliance computation when compliance cache is invalidate because of serialization when no serialization is asked to Unecessary compliance computations when historization of Node Compliance is disabled
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.16 which was released today.

Actions
Copy link

Also available in: Atom PDF