Learn about best practices to improve database performance and work efficiently with the database when deploying Adobe Commerce on cloud infrastructure.
Adobe Commerce on cloud infrastructure
Adobe recommends using the InnoDB database engine. In a default Adobe Commerce installation, all tables in the database are stored using the InnoDB engine. However, some third-party modules (extensions) can introduce tables in the MyISAM format. After you install a third-party module, check the database to identify any tables in
myisam format and convert them to
You can analyze the third-party module code before installing it, to determine if it uses MyISAM tables.
If you have already installed an extension, run the following query to determine whether the database has any MyISAM tables:
SELECT table_schema, CONCAT(ROUND((index_length+data_length)/1024/1024),'MB') AS total_size FROM information_schema. TABLES WHERE engine='myisam' AND table_schema NOT IN ('mysql', 'information_schema', 'performance_schema', 'sys');
db_schema.xml file declaring the table, set the
engine attribute value for the corresponding
table node to
innodb. For reference, see Configure declarative schema > table node in our developer documentation.
The declarative scheme was introduced in Adobe Commerce on cloud infrastructure version 2.3.
Adobe recommends that you always set up Elasticsearch or OpenSearch for your Adobe Commerce on cloud infrastructure project even if you plan to configure a third-party search tool for your Adobe Commerce application. This configuration provides a fallback option in case the third-party search tool fails.
The search engine you use depends on the Adobe Commerce on cloud version installed:
For Adobe Commerce 2.4.4 and later, use the OpenSearch service for native MySQL search.
For earlier Adobe Commerce versions, use Elasticsearch.
To determine which search engine is currently in use, run the following command:
./bin/magento config:show catalog/search/engine
For configuration instructions, see the Developer Guide for Adobe Commerce on cloud:
Avoid using custom triggers if possible.
Triggers are used to log changes into audit tables. Adobe recommends configuring the application to write directly to the audit tables instead of using the trigger functionality for these reasons:
To learn about alternatives to using custom triggers, see Use MySQL triggers effectively in our support knowledge base.
To avoid potential issues with cron deadlocks, upgrade ECE-Tools to version 2002.0.21 or higher. For instructions, see Update
ece-tools version in our developer documentation.
Switching indexers generates data definition language (DDL) statements to create triggers which can cause database locks. You can prevent this issue by putting your website in maintenance mode and disabling cron jobs before changing the configuration.
For instructions, see Configure indexers in the Adobe Commerce Configuration Guide.
Avoid running DDL statements in the Production environment to prevent conflicts (like table modifications and creations). The
setup:upgrade process is an exception.
If you need to run a DDL statement, put the website in maintenance mode and disable cron (see the instructions for switching indexes safely in the previous section).
Enable order archiving from the Admin to reduce the space required for Sales tables as your order data grows. Archiving saves MySQL disk space and improves checkout performance.
See Enable archiving in the Adobe Commerce Merchant documentation.