<\/p>\n Cache Type\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Description<\/p>\n Clean or flush this cache type after modifying configuration files.<\/td>\n<\/tr>\n Clean or flush this cache type after modifying layout files.<\/td>\n<\/tr>\n Clean or flush this cache type after modifying the view layer.<\/td>\n<\/tr>\n If necessary, Magento cleans up this cache automatically, but third-party developers can put any data in any segment of the cache.<\/p>\n Clean or flush this cache type if your custom module uses logic that results in cache entries that Magento cannot clean.<\/td>\n<\/tr>\n If necessary, Magento cleans up this cache automatically, but third-party developers can put any data in any segment of the cache.<\/p>\n Clean or flush this cache type after you make custom changes to the database schema. (In other words, updates that Magento does not make itself.).<\/td>\n<\/tr>\n You should not typically need to clean or flush this cache type.<\/td>\n<\/tr>\n If necessary, Magento cleans up this cache automatically, but third-party developers can put any data in any segment of the cache.<\/p>\n Clean\/flush this cache type after modifying code level that affects HTML output.<\/p>\n It\u2019s recommended to keep this cache enabled because caching HTML improves performance significantly.<\/td>\n<\/tr>\n Clean or flush this cache after changing or adding integrations.<\/td>\n<\/tr>\n <\/p>\n Read more: How to purge varnish cache remotely when using cloudflare<\/a><\/em><\/p>\n Read more: Amazon Elastic Cache : Make your applications faster<\/a><\/em><\/p>\n Read more : Magento Speed Optimization.<\/a><\/em><\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":"![\"\"](\"http:\/\/cloudkul.com\/blog\/wp-content\/uploads\/2017\/04\/system-magento2.png\")
<\/a><\/p>\n\n
<\/a><\/p>\n\n
<\/a><\/p>\n“voila it’s done”<\/em><\/h3>\n
Magento 2 has the following cache types<\/h2>\n
\n
\n\n
\n <\/th>\n <\/th>\n<\/tr>\n \n Configuration<\/td>\n Magento 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.<\/p>\n \n Layout<\/td>\n Compiled page layouts (that is, the layout components from all components).<\/p>\n \n Block HTML output<\/td>\n HTML page fragments per block.<\/p>\n \n Collections data<\/td>\n Results of database queries.<\/p>\n \n DDL<\/td>\n Database schema.<\/p>\n \n Entity attribute value (EAV)<\/td>\n Metadata related to EAV attributes (for example, store labels, links to related PHP code, attribute rendering, search settings, and so on).<\/p>\n \n Page cache<\/td>\n Generated HTML pages<\/p>\n \n Reflection<\/td>\n Removes a dependency between the Webapi module and the Customer module.<\/td>\n<\/tr>\n \n Translations<\/td>\n Merged translations from all modules.<\/td>\n<\/tr>\n \n Integration configuration<\/td>\n Compiled integrations.<\/p>\n \n Integration API configuration<\/td>\n Compiled integration APIs.<\/td>\n<\/tr>\n \n Web services configuration<\/td>\n Web API structure.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n