Project

General

Profile

Bug #16643

Unecessary compliance computations when historization of Node Compliance is disabled

Added by Nicolas CHARLES 8 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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

#1

Updated by Nicolas CHARLES 8 months ago

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

Updated by Nicolas CHARLES 8 months 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
#3

Updated by Nicolas CHARLES 8 months ago

  • Status changed from Pending technical review to Pending release
#6

Updated by Nicolas CHARLES 8 months 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
#7

Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

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

Also available in: Atom PDF