Actions
Bug #15749
closed
Use less memory in PreUnmarshallCheckConsistency
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
When we receive inventories, a lot of allocations and memory retained seems to come from the PreUnmarshallCheckConsistency - especially from checkNodeSeq when from checkInAgentTag and checkInRudderTag
we could probably extract once the Rudder and the Agent part, and deal with it in the relevants pre-s
Files
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years 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/2472
Updated by François ARMAND about 5 years ago
- Related to Bug #15758: Add -XX:+UseStringDeduplication in G1GC optionnal config added
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|bef679c090c8673430b64fdf2eeda48c00ac1668.
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 5 years ago
- Subject changed from A lot of memory (and ressources) seems to be used in PreUnmarshallCheckConsistency to Use less memory in PreUnmarshallCheckConsistency
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.14 which was released today.
Actions