Project

General

Profile

Actions

Bug #9854

closed

Slow compliance computation in Rudder 4.0

Added by Nicolas CHARLES almost 8 years ago. Updated over 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In Rudder 4.0 we can have slowness in compliance computation.

This is the parent ticket for the several found issues


Subtasks 3 (0 open3 closed)

Bug #9856: MergeCompareByRule is called for each nodes, and can add up to slow complianceRejected2016-12-26Actions
Bug #9857: ReportingServiceImpl moves around a lot of data and is fairly slowReleasedVincent MEMBRÉActions
Bug #9864: getNodeStatusReports is called for each node, and is slow to compute PolicyMode InconsistencyRejectedFrançois ARMAND2016-12-28Actions
Actions #1

Updated by Nicolas CHARLES almost 8 years ago

  • Description updated (diff)
Actions #2

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 4.0.3 to 4.0.4
Actions #3

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to Pending technical review
Actions #4

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Pending technical review to Released

All sub issues are solved

Actions

Also available in: Atom PDF