Project

General

Profile

Actions

Architecture #19151

closed

Architecture #18092: Improve compliance performance and reliability

add caching for NodeExpectedReports

Added by Nicolas CHARLES about 3 years ago. Updated almost 3 years ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:

Description

the expected reports are fairly expensive to get from the database, both for the db and resource intensive to deserialize
we should have a cache for it, with current expected reports, as well as the last one received from the node (which can be optional)


Subtasks 1 (0 open1 closed)

Architecture #19633: deletenode is used by scaleoutrelayReleasedAlexis MoussetActions
Actions #1

Updated by Nicolas CHARLES about 3 years ago

  • Subject changed from add cachng for NodeExpectedReports to add caching for NodeExpectedReports
Actions #2

Updated by Nicolas CHARLES about 3 years ago

  • Status changed from New to In progress
Actions #7

Updated by Nicolas CHARLES almost 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/3728
Actions #8

Updated by Nicolas CHARLES almost 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #16

Updated by Vincent MEMBRÉ almost 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.0.0~beta1 which was released today.

Actions

Also available in: Atom PDF