Optimizing the database and caching sql queries in OpenCart 2.0-2.2
Optimizing the database of an online store is a very difficult issue that sometimes requires separate research.
And the most unpleasant thing in this process is that only someone who knows sql-queries and understands databases (DB) can do at least some optimization.
Just so that clients don’t have to do what they don’t need to know, IMDBOptimizer was created. Capabilities:
1. A hybrid system for caching SQL queries (DB + files), which allows to increase the speed of HTML-page generation (tested on standard OpenCart with 5500 products – performance gain from 30% to 70-80%) and partially balance the load between the disk and the database.
2. Supported filter “by words” to exclude SQL queries from the caching process (case insensitive).
3. The filter “by URL” is supported to exclude individual pages from the caching of SQL queries (case insensitive).
4. Since only SQL queries are cached, such a module can be successfully used in conjunction with other caching modules (for example, v2pagecache). However, it is best to check compatibility on a test server.
5. Have you installed the module? You don’t need to configure anything for caching. SQL queries are automatically cached (based on filters), without the need to configure anything else.
6. Another distinctive feature of caching of SQL queries is that if the same query is used to generate different web pages or is simply executed repeatedly, then only one cache is used. A simple example, opened the same product from different categories – options will be cached only 1 time.
7. Can be used with or without index creation.
8. During installation, the module immediately creates a typical setting, you just need to enable the cache.
9. Easy to turn on and easy to turn off. Limitations and nuances:
1. Since this is a module for caching the level of the database, it must be borne in mind that such features as displaying the real balance of the product or the current price in the card are not supported (the data is cached).
2. Only SQL queries starting with select are cached.
3. Replaced core file registry.php
4. Caching is applied only to the client side, in the admin area all requests are executed as usual.
5. Be aware that caching is an overhead. For example, when you first open a product page, it may take longer to load (cache is created).
