The performance of the ElementCriteriaModel for lookups is killing me.
I have 300 or so "People" entries in a craft site and trying to load them just for a basic listing page takes forever. There's just so much overhead.
In this case of i.e. a listing page, I need the entry title, slug and an image field (which I'm eager loading). I don't need all of the other fields and overhead it loads.
Is there a way to get more acceptable performance for cases like this specific one (listing page with large number of entries and limited data needed)? Or am I going to have to bypass the element criterea stuff and do the lookups myself in SQL?
Thanks
ElementCriteriaModel
. I ran into this recently, with Categories. EachElementModel
occupies an awful lot of memory, and there's no way to create a "partial" model from anElementCriteriaModel
query.