Closed rwb196884 closed 3 weeks ago
Can you please check the joined tables. Do you have a large number of rows in (one of) them? And if so are these necessary?
I've got it down by removing some CORS origins and redirect URLs, but it's really not great that this thing can explode with really very few records.
We had performance issues with this query before in the ClientStore
implementation. Most problems were solved by switching to split queries in EF avoiding a cartesian explosion resulting in the many rows you're seeing.
Can you please try that and see if that works for you?
Clients.Select(z => z.ToModel()).AsSplitQuery())
If this query is used in a custom ClientStore
you can alternatively or in addition also enable caching.
Ah, that sounds like what I need; didn't know about that. Thank you.
writes the query
which with even a small amount of data (6 clients) can produce tens of thousands of rows -- and the query then times out while doing the sorting.