Project

General

Profile

Actions
Copy link

Bug #15648

closed

ComplianceLevels number keep growing in memory

Added by Nicolas CHARLES about 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
5.0.18
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

With 4500 nodes, and pleinty of reports, i'm seeing an increase in the total number of allocated ComplianceLevels, from

 5:       2231674      232094096  com.normation.rudder.domain.reports.ComplianceLevel

to
 2:       2990319      310993176  com.normation.rudder.domain.reports.ComplianceLevel

in 40 minutes

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #15646: Huge quantity of memory not released after generationReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 5 years ago

this may (or may be not) relatee to CachedReportingServiceImpl analyzed to be 1GB in size

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 5 years ago

  • Parent task deleted (#15646)
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Related to Bug #15646: Huge quantity of memory not released after generation added
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #6

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #8

Updated by François ARMAND over 4 years ago

  • Status changed from New to Resolved

It was resolved at some point in 5.0 or 6.0 lifespan :)

Actions
Copy link

Also available in: Atom PDF