Answers.Body: <p>It all depends on your needs. If the features of the Matrix fields are enough for you, I'd definitely stick with Matrix. If you need nested or reusable blocks, then go for Neo.</p>
  <p>Neo adds 4 tables to the database, so it must use it at some point and create a little overhead.</p>
  <p>That being said, I think your primary focus to improve performance should be on implementing <a href="https://craftcms.com/docs/3.x/dev/eager-loading-elements.html" rel="nofollow noreferrer">eager-loading</a> (<a href="https://github.com/spicywebau/craft-neo/blob/master/docs/eager-loading.md" rel="nofollow noreferrer">Neo supports it too</a>), and, if it's not enough, leveraging the <a href="https://craftcms.com/docs/3.x/dev/tags.html#cache" rel="nofollow noreferrer"><code>{% cache %}</code> twig tag</a>.</p>
  <p>And as James Smith pointed, using a third-party plugin is always a risk to consider when working on a large project.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-08T08:12:59.227Z
Answers.LastActivityDate: 2021-12-08T08:12:59.227Z
Answers.UserDisplayName: nstCactus
Answers.Body: <p>You should also consider Vizy:
  <a href="https://verbb.io/craft-plugins/vizy/features" rel="nofollow noreferrer">https://verbb.io/craft-plugins/vizy/features</a></p>
  <p>Very performant and nice to use for your editors.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-12-08T21:48:43.100Z
Answers.LastActivityDate: 2021-12-08T21:48:43.100Z
Answers.UserDisplayName: Matthias Redl-Mann
Body: <p>Simple question: Which field type is more <em>performant</em>, Matrix or Neo?</p>
  <p>I have to build a 60+ multi-site with different languages and I need to think about this architecture before building the <em>pageParts</em>.</p>
  <p>Does anyone know which one of these fields uses fewer resources on the database?</p>
  <p>Thank you</p>
  <p>LE: I have found this:</p>
  <p><em>Performance
  Out of the box, a Craft Matrix re-saves every block within that Matrix. If you have dozens of fields then this can take a lot of resources, meaning it takes a while to save. Ben (author of Neo) has built-in a superb feature in which the Neo field detects what is new and only saves the newly created content within the fields. Clever stuff!</em></p>
  <p>Is it true?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-12-07T16:49:28.447Z
Comments.Text: For such an enormous project, I would be much more concerned about stability/robustness/longevity, extensibility, and support options if things go wrong... I'm sure the Neo developers are wonderful in every regard, and will speedily update their plugin in line with changes to Craft and will never break core functionality or corrupt your content or expose your site to hackers, but personally I would never consider using a third-party plugin for such an integral part of your project.
Comments.UserDisplayName: James Smith
Tags: <matrix><plugin-neo>
Title: Matrix vs Neo, what should you use for 60+ multi site
ThreadText: # Matrix vs Neo, what should you use for 60+ multi site
  
  (Asked by: username_0 on 2021-12-07)
  
  Simple question: Which field type is more *performant*, Matrix or Neo?
  
  I have to build a 60+ multi-site with different languages and I need to think about this architecture before building the *pageParts*.
  
  Does anyone know which one of these fields uses fewer resources on the database?
  
  Thank you
  
  LE: I have found this:
  
  *Performance
  Out of the box, a Craft Matrix re-saves every block within that Matrix. If you have dozens of fields then this can take a lot of resources, meaning it takes a while to save. Ben (author of Neo) has built-in a superb feature in which the Neo field detects what is new and only saves the newly created content within the fields. Clever stuff!*
  
  Is it true?
  
  **Tags:** matrix, plugin-neo
  
  > **Comments:**
  > **username_1**: For such an enormous project, I would be much more concerned about stability/robustness/longevity, extensibility, and support options if things go wrong... I'm sure the Neo developers are wonderful in every regard, and will speedily update their plugin in line with changes to Craft and will never break core functionality or corrupt your content or expose your site to hackers, but personally I would never consider using a third-party plugin for such an integral part of your project.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2021-12-08. Score: 3 | Accepted answer
  
  It all depends on your needs. If the features of the Matrix fields are enough for you, I'd definitely stick with Matrix. If you need nested or reusable blocks, then go for Neo.
  
  Neo adds 4 tables to the database, so it must use it at some point and create a little overhead.
  
  That being said, I think your primary focus to improve performance should be on implementing [eager-loading](https://craftcms.com/docs/3.x/dev/eager-loading-elements.html) ([Neo supports it too](https://github.com/spicywebau/craft-neo/blob/master/docs/eager-loading.md)), and, if it's not enough, leveraging the [`{% cache %}` twig tag](https://craftcms.com/docs/3.x/dev/tags.html#cache).
  
  And as username_1 pointed, using a third-party plugin is always a risk to consider when working on a large project.
  
  
  ---
  
  ### Answer by username_3 on 2021-12-08. Score: 2
  
  You should also consider Vizy:
  <https://verbb.io/craft-plugins/vizy/features>
  
  Very performant and nice to use for your editors.
  
  
  ---
  
  