The Adobe Commerce and Magento Open Source cache management system provides an easy way to improve the performance of your site. Whenever a cache requires a refresh, a notice appears at the top of the workspace to guide you through the process. Follow the link to Cache Management and refresh the invalid caches.
When catalog entities are changed, it can affect other pages and invalidate multiple caches simultaneously. When you review the cache management page, you could see invalid items that require refresh when they were not edited directly. For example, this invalidation occurs when you edit any product in the catalog and it is assigned to any category, or when you change any related product rule.
After clearing a cache, always refresh your browser to make sure that you can see the most recent files. Clearing the Commerce cache does not clear your web browser cache. You may need to clear the browser cache to see updated content.
For additional technical information, see Cache overview in the Commerce Frontend Development Guide.
Access the Cache Management page by doing one of the following:
Reindexing and caching have different purposes in Commerce. Indexes track database information for increased search performance, faster data retrieval for storefronts, and more. Caches save loaded data, images, formats, and the like for increased performance loading and accessing the storefront.
Access to specific cache maintenance actions can be assigned to users by role, including options to view, toggle, and flush caches. Adobe recommends enabling flush actions only for administrator level users. Providing access to all Cache Management features can impact your storefront’s performance.
For information about assigning resources to grant access for Admin user accounts, see Role resources. The following resources control access to the cache management tools:
Clean Cache Actions
Cache Type Management
Additional Cache Management
For each cache to be refreshed, select the checkbox at the beginning of the row.
Set Actions to
Refresh and click Submit.
To select a group of caches, set Mass Actions to one of the following:
Select the checkbox of each cache to be targeted by the action.
Set Actions to
Refresh and click Submit.
Under Additional Cache Management, click Flush Catalog Images Cache to clear pre-generated product image files.
Image cache was cleaned message appears at the top of the workspace.
Clear the cache of your browser.
Clear the cache of your browser.
Commerce provides additional flush cache options using the command line. These options may require developer support to complete. For complete details and command options, see Manage the cache in the Configuration Guide.
|Mass Actions||Selects the checkbox of multiple caches. Options:
Select All — Selects the checkbox of all caches.
Unselect All — Clears the checkbox of all caches.
Select Visible — Selects the checkbox of all visible caches.
Unselect Visible — Clears the checkbox of all visible caches.
|Actions||Determines the action to be applied to all selected caches. Options:
Enable — Enables all selected caches.
Disable — Disables all selected caches.
Refresh — Refreshes all selected caches.
|Submit||Applies the action to all selected caches.|
|Flush Magento Cache||Removes all items in the default Commerce cache (
|Flush Cache Storage||Removes all items from the cache, regardless of Commerce tag. If your system uses an alternate cache location, any cached files used by other applications are removed in the process.|
|Flush Catalog Images Cache||Removes all automatically resized and watermarked catalog images that are stored in
|Flush Static Files Cache||Removes preprocessed view files and static files.|
|Configuration||Various XML configurations that were collected across modules and merged.
|Layouts||Layout building instructions.||
|Blocks HTML output||Page blocks HTML.||
|Collections Data||Collection data files.||
|Reflection Data||Clears API interface reflection data, that typically is generated during runtime.||
|Database DDL operations||Results of DDL queries, such as describing tables or indexes.||
|Compiled Config||Results of code compilation.||
|EAV types and attributes||Entity types declaration cache.||
|Customer Notification||Temporary notifications that appear in the user interface.||
|Integrations Configuration||Integration configuration file.||
|Integrations API Configuration||Integrations API configuration file.||
|Page Cache||Full page caching.||
|Web Services Configuration||REST and SOAP configurations, generated WSDL file.||
|Target Rule||Target Rule Index||
Adobe Commerce and Magento Open Source use full-page caching on the server to quickly display category, product, and CMS pages. Full-page caching improves response time and reduces the load on the server. Without caching, each page might need to run blocks of code and retrieve information from the database. However, with full-page caching enabled, a fully generated page can be read directly from the cache.
It is recommended that Varnish Cache be used only in a production environment.
Cached content can be used to process the requests from similar types of visits. As a result, pages shown to a casual visitor might differ from those shown to a customer. For the purposes of caching, each visit is one of three types:
Non-sessioned- During a non-sessioned visit, the shopper views pages, but does not interact with the store. The system caches the content of each page viewed and serves them to other non-sessioned shoppers.
Sessioned- During a sessioned visit, shoppers who interact with the store — through activities such as comparing products or adding products to the shopping cart — are assigned a session ID. Cached pages that are generated during the session are used only by that shopper during the session.
Customer- Customer sessions are created for those who have registered for an account with your store and shop while logged in to their accounts. During the session, customers can be presented with special offers, promotions, and prices that are based on their assigned customer group.
To configure the full-page cache:
On the Admin sidebar, go to Stores > Settings > Configuration.
In the left panel, expand Advanced and choose System.
Expand the Full Page Cache section.
Set Caching Application to one of the following:
To set the timeout for the page cache, enter the TTL for public content. (The default value is
If using Varnish, complete the Varnish Configuration section as follows:
Access list - Enter the IP addresses that can purge the Varnish configuration to generate a config file. Separate multiple entries with a comma. The default value is
Backend host - Enter the IP address of the backend host that generates config files. The default value is
Backend port - Identify the backend port that is used to generate config files. The default value is:
Grace period - Specify the number of seconds to use as a grace period to generate config files. See Advanced Varnish configuration in the Configuration Guide.
To export the configuration as a
varnish.vcl file, click the button for the version of Varnish that you use.
When complete, click Save Config.