Invalidating query cache entries key magento

28 Dec

The article is intended for fearless database beginners and designers who have been thrown in at the deep end.A database is basically a collection of tables of information, such as a list of customers and their orders.We’ve seen multiple installations with more or less random settings that we’ve traced back to blog posts where people have been testing various settings.For instance, there are options that you can enable that will work very well on a local area network but will break when clients are accessing the website across the internet.This article basically started with the site of a client who was having performance issues: when the cache reached about 38000 records, he was actually forced to clear the cache to keep the site responsive enough. Shouldn’t a full cache give a better performance then an empty cache?The number of records stored in the Magento cache depends on many factors, amongst others the number of store views, if a full page cache is used or not, and the size of the catalog.

Normalize the string and your cache hit rates will increase dramatically. Setting high TTLs without a proper plan The higher the TTL the better the speed of the website and the better the user experience.

I already explained the usage of My Isam, lack of transactions and lack of foreign keys but lets elaborate on the database a bit.

The purpose of this post is to spread knowledge about the bolts and gears of the Magento cache system among developers, and to share one method of overcoming some limitations of the file cache storage class.

Many Sites don’t go above 1000 or 2000 cache records, but for large instances much higher values are common.

The performance issues of my client only occurred on specific pages, one of the most noticeable being the add-to cart action.