Use the following strategies to reduce the number of categories:
Manage unique product features through attributes and custom options
Remove inactive categories
Optimize catalog depth in the navigation
Product attributes
Configuring too many product attributes or product attribute options can affect performance.
NOTE
Product attributes specify features that apply globally to all products. Product attribute options are customizations to specify features that apply to specific products.
SELECT COUNT(*) AS 'attribute_set' FROM *${TABLE_PREFIX}*eav_attribute_set;
Remove any unused attribute sets.
Potential performance impact
Configuring many product attributes increases the product template size for each product (EAV structure) and the amount of data that must be retrieved. This increase affects operations in the following ways:
Increase in SQL queries traffic related to EAV data retrieval and the amount of data processed which results in decreased DB throughput
Significant increase in the size of Adobe Commerce indexes and the full-text search index
Reaching hard MySQL limits when building a FLAT index for oversized product templates and inability to use it
Increases in product data and index sizes can affect site performance in the following ways:
Increased response time for most storefront scenarios related to catalog browsing, search (quick and advanced), and layered navigation.
Product management operations in the Admin slow significantly which can lead to timeouts.
Product Mass Actions functionality can be blocked.
Index re-build time for mid- and large-sized catalogs cannot be performed on a daily basis due to long execution times.
Configuring many attribute options can affect site performance in the following ways:
Long request and rendering times on product detail (PDP) and category pages containing complex products.
Admin product save operations response time increases above optimal performance targets.
Increase in Product Edit form rendering time.
Slow checkout.
Product options
Configuring too many product options per product can affect performance.
Use the following strategies to reduce the number of product options per product:
Configure complex products and custom options as a source of product variations.
Instead of creating global product templates and option containers that apply to all products, use attribute sets to build specific product templates with targeted attributes and options.
Manage product information through an external Product Management System (PMS).
Potential performance impact
Configuring many product options increases the amount of data retrieved for each product on all read and write operations resulting in:
Increased size for Adobe Commerce indexes and the full-text search index.
The increases listed above potentially affect site performance in the following ways:
Longer response time for most storefront scenarios related to products containing many options in attributes.
Significant increases in the time required to complete Product management operations in Admin that can lead to timeouts, especially for scenarios related to attributes list and tree retrieval including promotion rules management.
Can block bulk actions that complete asynchronous mass operations like import and export and assigning custom prices to multiple products in a shared catalog.
Product listing pagination
Displaying too many products per page can affect performance.
If you have too many products in a category, update the storefront catalog configuration to disable the option to Allow All Products per page.
After you disable this option, Adobe Commerce uses the product listing storefront pagination controls to manage the number of products that display in storefront components. For instructions, see Configure pagination controls.
Product SKU limits
Configuring too many product SKUs can affect performance by slowing down product data retrieval and increasing the time to complete Admin operations or indexations.
Use the following strategies to reduce the number of products (SKUs):
Minimize multipliers—
Consolidating websites reduces the multiplier.
Use alternative product features for custom pricing to replace shared catalog and customer groups multipliers.
Both customer groups and shared catalog function as multipliers for the number of effective SKUs in a store.
Restructure the catalog—
Reduce the number of products assigned to categories.
Decrease the number of SKUs by decreasing the number of websites, customer groups, shared catalogs, number of products, or number of configurable product options
Provide more product variations by using custom options instead of creating separate products.
Taking into account that an Effective SKU could include a number of potential permutation of prices, because prices can be specified differently per each store or customer group.
Deactivate or remove unused system components like modules. See Uninstall modules.
Manage products in an external Platform Management System (PMS).
Product variations
Configuring too many variations per product can affect performance.