Project

General

Profile

Actions

Bug #15675

closed

Leak in Cache of Node Compliance and NodeInfo and perfs improvement

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

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

There's a leak in Node Compliance cache - leaving Rudder alone for a night caused 51 millions of object in the map of CachedReportingServiceImpl, using a wooping 2 Go of RAM (the installation is REALLY large)

There's one also in the LocalNideInfoCache

It seems that mapValues references the initial map, causing it not to be GCable


Subtasks 2 (0 open2 closed)

Architecture #15676: Remove Map#keySet because of memory not freedRejectedNicolas CHARLESActions
Bug #15743: Millions of objects are instanciated while doing the policy generation for variable interpolationReleasedFrançois ARMANDActions

Related issues 4 (0 open4 closed)

Related to Rudder - Bug #16467: A lot of data is computed and stored in Policy object, that is either never used, or used only onceReleasedFrançois ARMANDActions
Related to Rudder - Bug #16468: Computation of ComplianceLevel generates too many objectsReleasedFrançois ARMANDActions
Related to Rudder - Bug #16513: JVM GC cannot clean objects in scope in a for { } yield {} even if they are not referenced anymoreReleasedFrançois ARMANDActions
Related to Rudder - Architecture #15678: Remove Map#mapValues because of memory not freedRejectedActions
Actions

Also available in: Atom PDF