Project

General

Profile

Actions

Bug #6194

closed

Add a cache for compliance by node

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

Status:
Released
Priority:
1
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

Node compliance takes a long time to compute (several seconds for ~1000 nodes).

And we exactly when they are updated: either on configuration modification, or when a new run comes.

So it's easy to build a cache and know when to invalidate it;

So let's do it and make Rudder fast.


Related issues

Related to Rudder - Bug #6184: Add a cache for recent changesReleasedNicolas CHARLES2015-01-27Actions
Actions #1

Updated by François ARMAND about 6 years ago

  • 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/805
Actions #2

Updated by François ARMAND about 6 years ago

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

Updated by Vincent MEMBRÉ about 6 years ago

  • Subject changed from Add a cach for compliance by node to Add a cache for compliance by node
Actions #5

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