Project

General

Profile

Actions

Bug #16643

closed

Unecessary compliance computations when historization of Node Compliance is disabled

Bug #16643: Unecessary compliance computations when historization of Node Compliance is disabled

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

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
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

Updated by Nicolas CHARLES almost 6 years ago Actions #1

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES

Updated by Nicolas CHARLES almost 6 years ago Actions #2

  • 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

Updated by Nicolas CHARLES almost 6 years ago Actions #3

  • Status changed from Pending technical review to Pending release

Updated by François ARMAND almost 6 years ago Actions #5

  • Fix check changed from To do to Checked

Updated by Nicolas CHARLES almost 6 years ago Actions #6

  • 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

Updated by Vincent MEMBRÉ almost 6 years ago Actions #7

  • Status changed from Pending release to Released

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

Actions

Also available in: PDF Atom