EF can have big problems with "Cartesian explosions" if an object has two lists of sub objects to return, it will get listA length x listB length items due to how the joins work. You can see how this leads to the explosion part of the name (with more objects or lists).

Their solution is a "split query" option, that does each sub table as a separate query, then seamlessly gives you the combined result.

If a change like this let's you get those different table lists as distinct lists with the processing and round trip time of multiple requests then it could be a game changer.

(Source - my last week 🤣😭 + lots of EF docs)