Bug #24652
closedRudder 8.1 slows down over time
Description
2024_03_16.stderrout.log.gz:2024-03-16 06:28:42+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 3893943 ms 2024_03_16.stderrout.log.gz:2024-03-16 07:32:03+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 3601104 ms 2024_03_16.stderrout.log.gz:2024-03-16 08:02:09+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 720472 ms 2024_03_16.stderrout.log.gz:2024-03-16 10:00:48+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 5868962 ms 2024_03_16.stderrout.log.gz:2024-03-16 12:01:45+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 6048786 ms 2024_03_16.stderrout.log.gz:2024-03-16 14:02:46+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 6057161 ms 2024_03_16.stderrout.log.gz:2024-03-16 17:49:57+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 7617380 ms 2024_03_16.stderrout.log.gz:2024-03-16 20:03:33+0000 DEBUG dynamic-group.timing - Computing dynamic groups without dependencies finished in 7807798 ms
There are objects ( com.normation.rudder.services.reports.CacheComplianceQueueAction$ExpiredCompliance ) piling up in the heap dump, which might be related
Files
Updated by Nicolas CHARLES 8 months ago · Edited
- Assignee set to Nicolas CHARLES
There are roughly 1 million of com.normation.rudder.services.reports.CacheComplianceQueueAction$ExpiredCompliance piling up in 30 minutes
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 8.1.0~rc1 to 8.1.0
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 8.1.0 to 8.1.1
Updated by François ARMAND 8 months ago
Creating an other ticket for the ExpiredCompliance which are pilling up, it might not be the root cause but something else to investigate
Updated by François ARMAND 8 months ago
- Related to Bug #24712: ExpiredCompliance events are pilling up added
Updated by François ARMAND 8 months ago
- Related to Bug #24713: Dynamic groups are slow to compute in Rudder 8.1 added
Updated by François ARMAND 8 months ago
- File clipboard-202404181612-sdcnh.png clipboard-202404181612-sdcnh.png added
- File clipboard-202404181623-dsmww.png clipboard-202404181623-dsmww.png added
We will need to see if the two linked tickets are enought to remove the slowdown over time.
After 24h on hour test machine, it seems to be ok with memory correctly reclamed when needed.
There is a lot of CPU spikes, they correlate with generation due to system-update campaign starting/ending.
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 8.1.1 to 8.1.2
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 8.1.2 to 8.1.3
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.3 to 8.1.4
Updated by François ARMAND 6 months ago
Perhaps we have a track to explore: the node score `handleEvent` that does a database insert is done in the `performAction` linked to the `invalidateComplianceReport` queue.
I'm going to try to move it in `fetchRunAndCompliance` around the place where `ComplianceRepository.saveRunCompliance` is done, which is known to be slow.
Updated by François ARMAND 6 months ago
- Status changed from New to In progress
- Assignee changed from Nicolas CHARLES to François ARMAND
Updated by François ARMAND 6 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5737
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.4 to 8.1.5
Updated by François ARMAND 6 months ago
- Assignee changed from Clark ANDRIANASOLO to Nicolas CHARLES
Updated by Anonymous 6 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|2a2d64a94af743234440725a992c02a468ffb6a6.
Updated by Vincent MEMBRÉ 5 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.5 which was released today.