Actions
Bug #15646
closed
Huge quantity of memory not released after generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
at the end of the generation, all nodeconfigurations are kept in memory, while they should be dismissed
in DeploymentService, we return the keyValues of the updatedNodeConfigs - andd it somehow keeps a reference to the map, preventing it to be garbage collected
on large install (3500 nodes with hundred of directives per nodes), it uses 3.5Go
It seems it was introduced in 5.0.9 or 5.0.10
Updated by 
Updated by 
Updated by
Actions