All Magento CLI commands must be run by the file system owner.
Commerce 2 has the following cache types:
|Cache type “friendly” name
|Cache type code name
|Commerce collects configuration from all modules, merges it, and saves the merged result to the cache. This cache also contains store-specific settings stored in the file system and database. Clean or flush this cache type after modifying configuration files.
|Compiled page layouts (that is, the layout components from all components). Clean or flush this cache type after modifying layout files.
|Block HTML output
|HTML page fragments per block. Clean or flush this cache type after modifying the view layer.
|Results of database queries. If necessary, Commerce cleans up this cache automatically, but third-party developers can put any data in any segment of the cache. Clean or flush this cache type if your custom module uses logic that results in cache entries that Commerce cannot clean.
|Database schema. If necessary, Commerce cleans up this cache automatically, but third-party developers can put any data in any segment of the cache. Clean or flush this cache type after you make custom changes to the database schema. (In other words, updates that Commerce does not make itself.) One way to update the database schema automatically is using the
magento setup:db-schema:upgrade command.
|Entity attribute value (EAV)
|Metadata related to EAV attributes (for example, store labels, links to related PHP code, attribute rendering, search settings, and so on). You should not typically need to clean or flush this cache type.
|Generated HTML pages. If necessary, Commerce cleans up this cache automatically, but third-party developers can put any data in any segment of the cache. Clean or flush this cache type after modifying code level that affects HTML output. It is recommended to keep this cache enabled because caching HTML improves performance significantly.
|Removes a dependency between the Webapi module and the Customer module.
|After merging translations from all modules, the merger cache will be cleaned.
|Compiled integrations. Clean or flush this cache after changing or adding integrations.
|Integration API configuration
|Compiled integration APIs configuration of the Store’s Integrations.
|Web services configuration
|Caching the Web API Structure.
|Temporary notifications that appear in the user interface.
|Admin UI SDK Cache
|Caches Admin customizations that were added with the Adobe Commerce Admin UI SDK.
|Webhooks Response Cache
|Caches responses to webhook requests.
To view the status of the cache, enter
A sample follows:
This command enables you to enable or disable all cache types or only the ones you specify. Disabling cache types is useful during development because you see the results of your changes without having to flush the cache; however, disabling cache types has an adverse effect on performance.
Starting in version 2.2, you can only enable or disable cache types using the command line while running Commerce in production mode. If running Commerce in developer mode, you can enable or disable cache types using the command line or manually. Before doing so, you must manually make
<magento_root>/app/etc/env.php writeable by the file system owner.
You can clean (also referred to as flush or refresh) cache types using either the command line or the Admin.
bin/magento cache:enable [type] ... [type]
bin/magento cache:disable [type] ... [type]
[type] enables or disables all cache types at the same time. The
type option is a space-separated list of cache types.
To list cache types and their status:
For example, to disable the full page cache and the DDL cache:
bin/magento cache:disable db_ddl full_page
Changed cache status:
db_ddl: 1 -> 0
full_page: 1 -> 0
Enabling a cache type automatically clears that cache type.
As of version 2.3.4, Commerce caches all system EAV attributes as they are retrieved. Caching EAV attributes in this manner improves performance, because it decreases the amount of insert/select requests to the DB. However, it increases cache network size as well. Developers can cache custom EAV attributes by running the
bin/magento config:set dev/caching/cache_user_defined_attributes 1 command. This can also be done from the Admin while in Developer mode by setting Stores > Settings Configuration > Advanced > Developer > Caching Settings > Cache User Defined Attributes to Yes.
Multiple pages cache can be invalidated simultaneously and automatically without these entities editing. For example, when any product in the catalog is assigned to any category, or when any related product rule is modified.
To purge out-of-date items from the cache, you can clean or flush cache types:
Cleaning a cache type deletes all items from enabled Commerce cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Commerce uses.
Disabled cache types are not cleaned.
Always clean the cache after upgrading versions of Magento Open Source or Adobe Commerce, upgrading from Magento Open Source to Adobe Commerce, or installing B2B for Adobe Commerce or any module.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
Flush cache types if you have already tried cleaning the cache and you are still having issues that you cannot isolate.
bin/magento cache:clean [type] ... [type]
bin/magento cache:flush [type] ... [type]
[type] is a space-separated list of cache types. Omitting
[type] cleans or flushes all cache types at the same time. For example, to flush all cache types, enter
Flushed cache types:
You can also clean and flush cache types in the Admin. Go to System > Tools > Cache Management. Flush Cache Storage is equivalent to
bin/magento cache:flush. Flush Magento Cache is equivalent to