Actions
Bug #16283
closedwe are always computing compliance and byNodes on RuleStatusReport, even when it's not necessay
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
on tests in PR changing the val to lazy val makes it run from 3700ms to 2700ms
in most case, we should need compliance, but not ByNodes (used only in display)
Actions