Project

General

Profile

Bug #16468

Computation of ComplianceLevel generates too many objects

Added by Nicolas CHARLES 9 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

The computation of ComplianceLevel is realy inefficient, as it goes on creating many object.

original code was in https://github.com/Normation/rudder/pull/2648/files and is extracted for readability

Test perfs with original method shows:
Computes take ~2000µs first, then ~450µs after 100 iteration, total test is 97038 µs

New compute is ~1000µs for first iteration, ~300µs after 100 iteration, total test is 38208 µs

Old sum is 85µs -> 8µs, total cost 3083µs
New sum is 74µs -> 3µs, total cost 2069µs

JIT does wonder, but still it cannot eradicate all overhead


Related issues

Related to Rudder - Bug #15675: Leak in Cache of Node Compliance and NodeInfo and perfs improvementReleasedNicolas CHARLESActions
Related to Rudder - Bug #16496: StatusReportTest leads to inconsistant resultsReleasedVincent MEMBRÉActions
#1

Updated by Nicolas CHARLES 9 months ago

  • Related to Bug #15675: Leak in Cache of Node Compliance and NodeInfo and perfs improvement added
#2

Updated by Nicolas CHARLES 9 months ago

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

Updated by Nicolas CHARLES 9 months ago

  • Description updated (diff)
#4

Updated by Nicolas CHARLES 9 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/2692
#5

Updated by Nicolas CHARLES 9 months ago

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

Updated by François ARMAND 9 months ago

  • Related to Bug #16496: StatusReportTest leads to inconsistant results added
#9

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