Denys Moskalenko

Guys, it's been a year already, please take part in this issue

Any updates here?

Over the weekend, I will try to add SQL queries and execution times to our data set.

### The queries generated by Django on our dataset ## 1) Engagements ### Before Execution time: ~40 s ``` SELECT "dojo_test"."id", "dojo_test"."engagement_id", "dojo_test"."lead_id", "dojo_test"."test_type_id", "dojo_test"."scan_type", "dojo_test"."title", "dojo_test"."description", "dojo_test"."target_start", "dojo_test"."target_end", "dojo_test"."estimated_time",...

Sry, I have been on the vacation, will continue working this PR this week. 1) About this (https://github.com/DefectDojo/django-DefectDojo/pull/12603#issuecomment-2982864693) - I mean the secondary ordering, i see it's different from initial...

> valentijnscholten I have added new commit with changes you asked before

I just run the query on our dataset (We have **387** products with total ~**1.2kk** findings overall, few products has 250k and 150k findings, other 100-7k If we open the...

Hi @gietschess , Following up on the discussion in https://github.com/DefectDojo/django-DefectDojo/issues/12575: we’ve applied the same counter-optimisation technique to the products query. Although performance on that query wasn’t a major pain point...

I found a few more places where we have a problem, I'll open PRs for those too.

> @DenysMoskalenko Thank you again for your contributions. I've moved this to the 2.49.0 while we wait for conflicts resolution. Thanks, I will fix the conflicts. Also I really want...