Project

General

Profile

Actions
Copy link

Bug #20367

closed

Bug #20366: get rules/tree and get groups/tree are very slow

first go at improving perfs for rules/tree

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

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
7.0.0~rc2
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

the costly part is really to get the NodeInfo from the computed NodeIds in getRuleApplicationStatus, then if the rule is applied ( applicationService.isApplied(rule,groupLib,directiveLib,nodesLib) ) and then computing the policymode ( ComputePolicyMode.ruleMode(globalMode, directives.map(._2), nodes.map(.policyMode)) )

Actions
Copy link
 #1

Updated by Nicolas CHARLES about 3 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Nicolas CHARLES about 3 years ago

  • Target version changed from 6.2.12 to 7.0.0~rc2

actually code is only in 7.0

Actions
Copy link
 #3

Updated by Nicolas CHARLES about 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/4039
Actions
Copy link
 #4

Updated by Nicolas CHARLES about 3 years ago

this improves from 9s to 4s the rules/tree

Actions
Copy link
 #5

Updated by Nicolas CHARLES about 3 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 3 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF