Skip to main content
Magento

Return to Answer

Bolded the important statement in this answer
Source Link
Josh Davenport-Smith
Josh Davenport-Smith
  • 959
  • 1
  • 10
  • 22

As of Magento 2.3, it is no longer best practice to use the flat catalog at all.As of Magento 2.3, it is no longer best practice to use the Flat Catalog feature at all.

Detailed info and justificationThe primary justfication for this are a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specificallyrevolves around forthis official troubleshooting article that recognises ongoing performance reasonsissues. As this question is relatedThe official docs links to performancethat article. Also, the Magento 2.3/2.4 docs now show an official stance on this is relevant.

Magento 2 flat catalog optimization:

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.Magento docs content

Some tweets that start toare relevant, they shed some light on this change when we first discovered this change in tact from the Magento team and still now contain some interesting thoughts:

As of Magento 2.3, it is no longer best practice to use the flat catalog at all.

Detailed info and justification for this are a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specifically for performance reasons. As this question is related to performance, this is relevant.

Magento 2 flat catalog optimization

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

As of Magento 2.3, it is no longer best practice to use the Flat Catalog feature at all.

The primary justfication for this revolves around this official troubleshooting article that recognises ongoing performance issues. The official docs links to that article. Also, the Magento 2.3/2.4 docs now show an official stance on this:

Magento docs content

Some tweets that are relevant, they shed light on this change when we first discovered this change in tact from the Magento team and still now contain some interesting thoughts:

Improving the answer
Source Link
Rafael Corrêa Gomes
Rafael Corrêa Gomes
  • 13.7k
  • 14
  • 91
  • 181

As of Magento 2.3, it is no longer best practice to use the flat catalog at all.

Detailed info and justification for this isare a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specifically for performance reasons. As this question is related to performance, this is relevant.

enter image description hereMagento 2 flat catalog optimization

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

As of Magento 2.3 it is no longer best practice to use flat catalog at all.

Detailed info and justification for this is a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specifically for performance reasons. As this question is related to performance, this is relevant.

enter image description here

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

As of Magento 2.3, it is no longer best practice to use the flat catalog at all.

Detailed info and justification for this are a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specifically for performance reasons. As this question is related to performance, this is relevant.

Magento 2 flat catalog optimization

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

Added basic references, reworded for brevity
Source Link
Josh Davenport-Smith
Josh Davenport-Smith
  • 959
  • 1
  • 10
  • 22

InfoAs of Magento 2.3 it is no longer best practice to use flat catalog at all.

Detailed info and justification for this is a little thin on the ground right now (updates should be made to answers here to reflect when more info is found) but as of Magento 2.3 it is no longer best practice to use flat catalog.) Apparently, this is forspecifically for performance reasons, as the. As this question is related to performance, this is relevant.

enter image description here

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

Info is a little thin on the ground right now (updates should be made to answers here to reflect when more info is found) but as of Magento 2.3 it is no longer best practice to use flat catalog. Apparently, this is for performance reasons, as the question is related to performance, this is relevant.

enter image description here

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

As of Magento 2.3 it is no longer best practice to use flat catalog at all.

Detailed info and justification for this is a little thin on the ground right now (updates should be made to answers here to reflect when more info is found.) Apparently, this is specifically for performance reasons. As this question is related to performance, this is relevant.

enter image description here

Whatever issues the Magento team have found with flat catalog must outweigh the benefits of converting EAV data to a flat structure.

Some tweets that start to shed some light on this:

Source Link
Josh Davenport-Smith
Josh Davenport-Smith
  • 959
  • 1
  • 10
  • 22