Project

General

Profile

Actions

Bug #6184

closed

Add a cache for recent changes

Added by François ARMAND about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Performance and scalability
Target version:
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


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #6194: Add a cache for compliance by nodeReleasedNicolas CHARLES2015-01-28Actions
Actions #1

Updated by François ARMAND about 9 years ago

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)

Actions #2

Updated by François ARMAND about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ about 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

Actions

Also available in: Atom PDF