Actions
Bug #16201
closedInefficient computing of compliance on home page
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:
Description
On home page, we compute the compliance in two ways:
- Once by searching all rules non system, getting the compliance of these rules
- Once by getting the reports of all node, filtering out the reports linked to system directive, and getting the compliance out of these
The second one takes 15s in the filtering, and both approach looks really similar. Maybe we are really doing twice the same query, but it seems odd
We need to validate the result of both computation, to check that there are indeed similar or dissimilar, and then merge them if necessary
Also, getting the node last run is not batched, so we are doing one big query that is probably memory bound (and too intensive on the db)
Actions