Improve reporting performance #12771
Description
Some users report poor performance on the reporting options on bigger instances
I'm experiencing issues with my report tab in the UI, and when I attempt to create a report directly from the open findings with more than a certain number of vulnerabilities, the creation process times out. Do you know if there is some known issue regarding that or not? I explored a bit of the code and I think the issue relies on the fact that before generating the HTLM report, Django evaluates the entire findings.qs queryset. This means it loads all the vulnerability objects from the database into the server's RAM simultaneously.
Desired behaviour
More efficient reporting.
We would welcome community contributions on this.