Answers.Body: <p>In a previous project when I was in dev mode, the website was very slow. But when I shut this down it was fast again. Could this be a solution?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-13T14:22:23.280Z
Answers.Text: Thank you so much for this answer!!! I have been trying to figure out for the last week why Craft has been so slow with any matrix fields on my channels -- this is definitely why! Maybe it's due to logging all database stuff?
Answers.UserDisplayName: Sandy D.
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-02-19T23:31:25.190Z
Answers.LastActivityDate: 2016-02-19T23:31:25.190Z
Answers.UserDisplayName: Martijn La Feber
Body: <p>I'm implementing a site with just one very big matrix field called 'blocks', and all my frontend is designed with BEM CSS with a lot of components.</p>
  
  <p>But i'm facing problems with this big field.</p>
  
  <p>1) If two block types have a field called 'cssClasses' of type 'Multi-select', it's not validating correctly and is saving just one of this fields. I've found a workaround, changing the name of second field, but frequently i lost a lot of field values with this problem. (i really don't know exactly why this problem is happening sometimes)</p>
  
  <p>2) If i have too many fields on my block items, there are some implicit field limit that i don't know where is, that all block item fields after this limit are deleted when save... its a very big problem, because all my entries loose all the data for these fields. It's really a big problem for me... (maybe can be max_input_vars value and/or post_max_size)</p>
  
  <p>3) It's very slow to page render this big field when testing on Amazon(rds large + 1000 IOPS SSD) or Heroku (clearbit database high io), compared to my localhost.</p>
  
  <p>PS: 
  I'm using LinkIt plugin and SuperTable plugin for some fields...</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-16T19:57:04.527Z
Comments.Text: #2 is definitely related to max_input_vars value and/or post_max_size.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-02-10T23:46:15.813Z
Comments.Text: I ran into issue #2 today, and it was definitely due to max_input_vars. @BradBell would it be possible to change how Craft posts data when saving a matrix field? It seems like just serializing it before the submission and then deserializing in the controller would address this issue without people needing to know to update their PHP settings, since the matrix field definition would always just be a single variable.
Comments.UserDisplayName: John O
Tags: <matrix>
Title: Saving big matrix fields problems
ThreadText: # Saving big matrix fields problems
  
  (Asked by: username_0 on 2015-11-16)
  
  I'm implementing a site with just one very big matrix field called 'blocks', and all my frontend is designed with BEM CSS with a lot of components.
  
  But i'm facing problems with this big field.
  
  1) If two block types have a field called 'cssClasses' of type 'Multi-select', it's not validating correctly and is saving just one of this fields. I've found a workaround, changing the name of second field, but frequently i lost a lot of field values with this problem. (i really don't know exactly why this problem is happening sometimes)
  
  2) If i have too many fields on my block items, there are some implicit field limit that i don't know where is, that all block item fields after this limit are deleted when save... its a very big problem, because all my entries loose all the data for these fields. It's really a big problem for me... (maybe can be max\_input\_vars value and/or post\_max\_size)
  
  3) It's very slow to page render this big field when testing on Amazon(rds large + 1000 IOPS SSD) or Heroku (clearbit database high io), compared to my localhost.
  
  PS:
  I'm using LinkIt plugin and SuperTable plugin for some fields...
  
  **Tags:** matrix
  
  > **Comments:**
  > **username_1**: #2 is definitely related to max_input_vars value and/or post_max_size.  
  > **username_2**: I ran into issue #2 today, and it was definitely due to max_input_vars. @username_1 would it be possible to change how Craft posts data when saving a matrix field? It seems like just serializing it before the submission and then deserializing in the controller would address this issue without people needing to know to update their PHP settings, since the matrix field definition would always just be a single variable.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2016-02-19. Score: 2
  
  In a previous project when I was in dev mode, the website was very slow. But when I shut this down it was fast again. Could this be a solution?
  
  > **Comments:**
  > **username_4**: Thank you so much for this answer!!! I have been trying to figure out for the last week why Craft has been so slow with any matrix fields on my channels -- this is definitely why! Maybe it's due to logging all database stuff?  
  
  ---
  
  