Actions
Bug #6184
closed
Add a cache for recent changes
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In Rudder 3.0, we display graphes of recent changes for rules (by default, for the last 3 days by interval of 6 hours).
Their can be A LOT of them, making the DB query possibly EXTREMLLY long, and we know exactly when some are added (since at least, we are producing non-compliance-logs).
So, we need a cache for them.
Files
| Rudder_-_Rules_Management_-_2015-01-27_20.55.04.png (10.6 KB) Rudder_-_Rules_Management_-_2015-01-27_20.55.04.png |
Updated by François ARMAND almost 10 years ago
- File Rudder_-_Rules_Management_-_2015-01-27_20.55.04.png Rudder_-_Rules_Management_-_2015-01-27_20.55.04.png added
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/804
the PR is here:
https://github.com/Normation/rudder/pull/804
The code can be reviewed for the logic & all, but something seems broken in the display of graphe (see screenshot)
Updated by François ARMAND almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 48cd57817e541b87fea1d61894a08d575deb5db7.
Updated by Nicolas CHARLES almost 10 years ago
Applied in changeset fcc732510da179b761fc3ec5b5c0543981d781fd.
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions