Whenever one or more items change, Magento reindexes automatically. Any action such as price changes, creating catalog or shopping cart price rules, adding new categories, and so on can activate reindexing. Magento accumulates data into special tables using indexers to optimize performance. The indexed tables must be updated or reindexed when the data changed. Your store remains accessible during the reindexing background processes.
Reindexing data boost speed of processing, and reduces the waiting time of the customer. For example, if you edit the price of a product from 4$ to 3$, Magento reindexes the data to display the price change in the store. Without indexing, Magento has to calculate the price of every product on the fly, taking into account shopping cart price rules, bundle pricing, discounts, tier pricing, and so on. Customers have to wait longer to see the product.
- Index Management has a slightly different presentation for flat product catalogs.
- To avoid problems when multiple Admin users update objects that trigger automatic reindexing, we recommend that you set all indexers to run on schedule as cron jobs. Otherwise, every time an object is saved, any objects with interdependencies might cause a deadlock. Symptoms of a deadlock include high CPU usage and MySQL errors. As a best practice, we recommend that you use scheduled indexing.
Follow these steps to change the index mode:
On the admin sidebar click System > Under Tools, click Index Management
Tick the checkbox to select indexer as you want, set action to Update on Save or Update by Schedule and click Submit to apply.
Above is a tutorial on how to configure index management in Magento 2 admin panel. We hope that you can optimize the loading progress of your website after reading this guideline. See you in the next article.
To display category, product, and CMS pages quickly, Magento Open Source uses full-page caching on the server. Full-page caching enhance response time and reduces the load on the server, Magento Open Source uses full-page caching 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.
We recommend using Varnish only in a production environment.
The system can use the cached content to process the requests from similar types of visits. Pages shown to a casual visitor might differ from those shown to a customer. For the purposes of caching, there are 3 types of visit:
Non-sessioned: During a non-sessioned visit, a customer 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 customers.
Sessioned: During a sessioned visit, customers 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 customer during the session.
Customer: Customer sessions are created for those who have registered for an account while logged in to their accounts. During the session, special offers, promotions, and prices that are based on the customer group to which they are assigned can be present to them.
For technical information, see Configure and Use Varnish and Use Redis for the Magento page and default cache in the developer documentation.
To configure the full-page cache, you can follow these steps:
- On the Admin sidebar, click Stores. Under Settings, click Configuration.
- On the left of the panel under Advanced, select System.
- Open the Full Page Cache tab
- Set Caching Application to one of these options:Built-in ApplicationVarnish Caching
- Enter the TTL for public content (the default value is 86400) to set the time-out for the page cache
- If using Varnish, complete the Varnish Configuration section as follows
- In the Access list field, 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 “localhost.”
- In the Backend host field, enter the IP address of the backend host that generates config files. The default value is “localhost.”
- In the Backend port field, identify the backend port that is used to generate config files. The default value is: “8080.”
- Click the button for the version of Varnish that you use to export the configuration as a varnish.vcl file, Export VCL for Varnish 3
Export VCL for Varnish 4
- Click Save Config
In this chapter, we will describe performing routine index and cache management operations, back-up the system, and use tools that help Support team troubleshoots and fix problems.
In Magento 2 default installation, the cache management system is an easy way to enhance the performance of your website. You can click the link to cache management and refresh the invalid caches instead of using the command code.
The status of each primary cache and its associated tag displayed in the Cache Management page. Refresh your browser after clearing cache to see the most recent files.
Cache Management Role Resources allows store administrators to assign access to specific cache maintenance actions to users.
- Follow these steps to refresh specific caches:
- Click the Cache Management link
- On the Admin sidebar click System > Cache Management
Mark the checkbox to select the cache you want to refresh, set the action to Refresh and click Submit.
- Follow these steps to mass action:
Set Mass Action to Select All or Select Visible, tick the checkbox of each cache to be targeted by the action, set action to refresh and click Submit.
- Follow these steps to flush the product image cache:
In the Cache Management page, click Flush Catalog Images Cache to delete pre-generated product image files. You will see the message “Image cache was cleaned”
Remember to also clear browser cache.
||Tick the checkbox of multiple caches. Options include
||Tick the checkbox of all caches.
||Clears the checkbox of all caches.
||Tick the checkbox of all visible caches.
||Clears the checkbox of all visible caches
||Decide the action to be applied to all selected caches. Options include:
||Enables all selected caches.
||Disables all selected caches.
||Refreshes all selected caches.
||Applies the action to all selected caches.
|Flush Magento Cache
||Deletes all items in the default Magento cache (var/cache), according to their associated Magento tags.
|Flush Cache Storage
||Deletes all items from the cache, regardless of Magento 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
||Deletes all automatically resized and watermarked catalog images that are stored at media/catalog/product/cache. If recently uploaded images aren’t reflected in the catalog, try flushing the catalog and refreshing your browser.
|Flush Static Files Cache
||Deletes preprocessed view files and static files.
Cache Management Role Resources
||Various XML configurations that were collected across modules and merged. Associated Tag: CONFIG
||Layout building instructions.
Associated Tag: LAYOUT_GENERAL_CACHE_TAG
|Blocks HTML output
||Page blocks HTML. Associated Tag: BLOCK_HTML
||Collection data files. Associated Tag: COLLECTION_DATA
||Clears API interface reflection data, that is typically generated during runtime.
|Database DDL operations
||Results of DDL queries, such as describing tables or indexes.
Associated Tag: DB_DDL
|EAV types and attributes
||Entity types declaration cache. Associated Tag: EAV
||Temporary notifications that display in the user interface.
||Integration configuration file. Associated Tag: INTEGRATION
|Integrations API Configuration
||Integrations API configuration file.
Associated Tag: INTEGRATION_API_CONFIG
||Full page caching. Associated Tag: FPC
||Translation files. Associated Tag: TRANSLATE
|Web Services Configuration
||REST and SOAP configurations generated WSDL file.
Associated Tag: WEBSERVICE
||Clean Cache Actions
Flush Cache Storage
Fluch Magento Cache
||Cache Type Management
Toggle Cache Type
Refresh Cache Type
||Additional Cache Management
Catalog Images Cache
Flush Static Files
In the previous article, we describe tutorial on configuring Browser Capabilities Protection. In this article, we will describe how to configure Action Log in Magento 2 admin panel.
The Action Log allows store administrators to track activities of other administrators in your stores. For most events, the action, the user who performed action, the result of the action, and the ID of the object on which the action was performed are included in the available information. Action Log is very important for your Magento 2 online store because you can track activities of administrators effectively and manage their actions. Furthermore, you can detect if hackers are hijacking right to control your website or not, and remove them out of your admin roles as fast as you can. So you have to configure action log and tracking every single action of other store administrators carefully.
To configure the Action Log, you have to follow these steps:
On the admin sidebar, click Stores. Under Settings, click Configuration.
On the left of the panel under Advanced, click Admin.
Open the Admin Actions Logging, select and mark any checkbox to enable actions logging as you want. There are 17 actions logs to choose in the global scope, so you have to choose wisely and do not miss anything.
Click Save Config after completed.
Above is a tutorial on how to configure action log in Magento 2 admin panel. We hope that you will know how to select action logs, oversee the action of other administrators carefully, manage other store administrators under your command and run your online store smoothly. If you have any question or have any edit request, feel free to leave a comment or contact us directly. In the next article, we will describe tools and cache management in Magento 2. See you in the next blog post.