Project

General

Profile

Actions

Bug #20318

closed

Improve performance of getUserAndSystemNodeStatusReports by exploring only once cache

Added by Nicolas CHARLES about 1 year ago. Updated 12 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Regression:

Description

we are calling twice findRuleNodeStatusReports, so we waste time by exploring twice the cache
https://issues.rudder.io/issues/20316

this has a peculiar impact in 7.0 where the API is used for node list


Subtasks 1 (0 open1 closed)

Bug #20380: upmerge of parent ticket broke 7.0ReleasedVincent MEMBRÉActions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #20316: Compliance is cached as a whole for all node, but used as System and User complianceRejectedActions
Actions #1

Updated by Nicolas CHARLES about 1 year ago

  • Related to Bug #20316: Compliance is cached as a whole for all node, but used as System and User compliance added
Actions #2

Updated by Nicolas CHARLES about 1 year ago

  • Status changed from New to In progress
Actions #3

Updated by Nicolas CHARLES about 1 year 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/4018
Actions #4

Updated by Nicolas CHARLES 12 months ago

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

Updated by Vincent MEMBRÉ 12 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.2.12 and 7.0.0~rc2 which were released today.

Actions

Also available in: Atom PDF