Answers.Body: <p>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.</p>
  
  <p>Relational fields have similar issues if you plan on <em>selecting</em> 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.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-19T20:48:23.497Z
Answers.LastActivityDate: 2014-08-19T20:48:23.497Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>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.</p>
  
  <p>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?</p>
  
Tags: <control-panel><performance>
Title: How might big Matrix/Relationship fields affect front-end CP performance?
ThreadText: # How might big Matrix/Relationship fields affect front-end CP performance?
  
  (Asked by: username_0 on 2014-08-19)
  
  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?
  
  **Tags:** control-panel, performance
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-08-19. Score: 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.
  
  
  ---
  
  