Actions
Bug #9857
closed
Bug #9854: Slow compliance computation in Rudder 4.0
ReportingServiceImpl moves around a lot of data and is fairly slow
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In findRuleNodeStatusReports, we have massive slowness in the creation of resulting NodeStatusReports, even if everything is correctly fetched from cache
Indeed, it recreates for each nodes NodeStatusReport and AggregatedStatusReports, and it easily take 9s for 1000 nodes, as the creation of these object involves a lot lot of merge, group, filter, etc
Updated by Nicolas CHARLES almost 8 years ago
- Subject changed from ReportingServiceImpl moved around a lot of data and is fairly slow to ReportingServiceImpl moves around a lot of data and is fairly slow
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1409
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|833beda413edf346581283cde2f2c5dab8ea4c50.
Updated by Vincent MEMBRÉ almost 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.3 and 4.1.0~beta3 which were released today.
- 4.0.3: Announce Changelog
- 4.1.0~beta3: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions