2

I frequently run into front-end performance issues in EE CP pages, where I have a big Matrix field (100+ rows), or a Playa field with a long list of entries (3000+ relatable entries), or worst of all, a combo of the two: The page gets really slow, and sometimes freezes, while JS initializes and renders all of those fields and their content.

I'm curious if the same issues would plague big Matrix/Relationship fields in Craft's CP. If not, what architectural differences make it so?

1

Matrix fields are going to suffer from similar scalability issues if you have a large number of blocks in a single field, affecting memory consumption, MySQL/Javascript performance, and usability. We consider that a bug (and it has been logged in our bug tracker as such), and plan on addressing it at some point in the future.

Relational fields have similar issues if you plan on selecting hundreds of elements. If you simply have a section with hundreds of entries, but don’t intend on actually selecting more than a handful, you don’t have anything to worry about; the element selector modal that comes up when you want to select additional elements is perfectly scalable, because it only loads 50 elements at a time, and lazy-loads additional elements as needed via an infinite scrolling implementation.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.