Project

General

Custom queries

Profile

Actions
Copy link

Bug #6194

closed

Add a cache for compliance by node

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

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Performance and scalability
Target version:
3.0.0
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 1 (0 open — 1 closed)

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

Added by François ARMAND about 10 years ago

Revision 7b4f1082 (diff)

Fixes #6194: Add a cach for compliance by node

Added by François ARMAND about 10 years ago

Revision 2f1e00ed (diff)

Fixes #6194: Add a cach for compliance by node

Added by Nicolas CHARLES about 10 years ago

Revision 9b61fd71

Merge pull request #805 from fanf/bug_6194/add_a_cach_for_compliance_by_node

Fixes #6194: Add a cach for compliance by node

Added by Nicolas CHARLES about 10 years ago

Revision 7b58dafb

Merge pull request #805 from fanf/bug_6194/add_a_cach_for_compliance_by_node

Fixes #6194: Add a cach for compliance by node

Actions
Copy link

Also available in: Atom PDF