Project

General

Profile

Actions
Copy link

Bug #24047

closed

Compliance has unoptimized usage of map view and policy mode computation

Added by Clark ANDRIANASOLO 10 months ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
8.1.0~beta1
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:
No

Description

In node group and node compliance, getting the policy mode re-computes some computation that is done earlier: getting node ids for a rule.

Some collection operations on node facts are also slow are they are re-computed every time instead of being stored in-memory

Related issues 2 (0 open — 2 closed)

Related to Rudder - User story #23935: API for node group complianceReleasedVincent MEMBRÉActions
Related to Rudder - Bug #24028: Add policy mode info in group compliance detailsReleasedRaphael GAUTHIERActions
Actions
Copy link
 #1

Updated by Clark ANDRIANASOLO 10 months ago

  • Related to User story #23935: API for node group compliance added
  • Related to Bug #24028: Add policy mode info in group compliance details added
Actions
Copy link
 #2

Updated by Clark ANDRIANASOLO 10 months ago

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

Updated by Clark ANDRIANASOLO 10 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/5334
Actions
Copy link
 #4

Updated by Clark ANDRIANASOLO 10 months ago

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

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF