by Ivan Kristianto 4.3 (12 reviews)

DB Cache Reloaded Fix

Name: DB Cache Reloaded Fix
Rating: 4.3 (12 reviews)
Author: Ivan Kristianto

The fastest cache engine for WordPress, that produces cache of database queries with easy configuration. Compatible with WordPress 3.4

DB Cache Reloaded Fix ranks #4,668 among WordPress.org plugins with 2,000+ active installations, is #163 of 1,523 in the Performance category, a 4.3/5 rating from 12 reviews, and was last updated Nov 28, 2017. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 3.4.2 (Current: 7.1)

v2.3 Current Version v2.3

Updated 8 years ago Last Update on 28 Nov, 2017

Refreshed 10 hours ago Last Refreshed on

#163 of 1,523 in Performance Top 10% by installs No update in over a year

View on WordPress.org

Rank

#4,668

-1 this week

Active Installs

2K+

-31.2%

KW Avg Position

N/A

— No change

Downloads

230.6K

+3 today

Support Resolved

— No change

Rating

86%

Review 4.3 out of 5

4.3 (12 reviews)

Next Milestone 3K

Total Progress 89.3%

2K+ 3K+

423

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 107 more installs to reach 3K+

Rank Changes

Current #4,668

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.3

12 reviews

Overall 86%

10 (83%)

0 (0%)

2 (17%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for DB Cache Reloaded Fix. Checked 1 month ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.3
Last Updated: Nov 28, 2017
Requires WP: 3.0+
Tested Up To: 3.4.2
PHP Version: N/A
Author: Ivan Kristianto

Support & Rating

Rating: ★ ★ ★ ★ ☆ 4.3
Reviews: 12
Support Threads: 0
Resolved: 0%

Keywords

cache caching db cache performance WP Cache

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,751

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Wordfence Security - Firewall, Malware Scan, and Login Security

Speed Optimizer - The All-In-One Performance-Boosting Plugin

1M+ installs

#43

WP Fastest Cache - WordPress Cache Plugin

1M+ installs

#47

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Performance plugins

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site owners who want faster page loads without relying on HTML caching plugins like WP-Cache or WP Super Cache. It solves the problem of slow database queries by caching them for a set lifetime, reducing server CPU load and disk usage compared to alternatives.

Caches database queries
Configurable cache lifetime
Lower disk space usage
Reduces server CPU load
Multiple language translations
WordPress 3.4 compatibility

Frequently Asked Questions

Common questions about DB Cache Reloaded Fix

Check your cache directory wp-content/tmp/ for cache files. Check the load statistics in footer. Also you can set DBCR_DEBUG to true in db-cache-reloaded.php file to display as hidden comments on your html page, what queries were loaded from cache and what from mysql. You can also define DBCR_SAVEQUERIES in wp-config.php file - it works similarly as defining SAVEQUERIES, but DB Cache Reloaded adds one extra field to the $wpdb->queries array - boolean value indicating if query was executed directly (false) or loaded from cache (true). Of course you can also use some extra code (e.g. some plugin) do display this data.

This plugin decreases count of queries to DB, which means that CPU load of your web-server decreases and your blog can serve much more visitors in one moment.

It is time from request to server (start of generation) and the generated page sent (end of generation). This time depends on server parameters: CPU speed, RAM size and the server load (how much requests it operates at the moment, popularity of sites hosted on the server) and of course it depends on how much program code it needs to operate for page generation. Let set the fourth parameter as constant (we can't change the program code). So we have only 3: CPU, RAM and popularity. If you have a powerful server (costs more) it means that will be as low as possible and it can serve for example 100 visitors in one moment without slowing down. And another server (low cost) with less CPU speed and RAM size, which can operate for example 10 visitors in one moment. So if the popularity of your site grows it is needed more time to generate the page. That's why you need to use any caching plugins to decrease the generation time.

You can show usage statistics with your custom template in your footer. Checking count of queries, ensure that other cache plugins are disabled, because you can see cached number. View the source of your site page, there maybe some code like this at the foot:  If not, please put these codes in your footer template:  After using the DB Cache Reloaded, I think you'll find the number of queries reducing a lot.

This plugin is based on a fundamentally different principle of caching queries to database instead of full pages, which optimises WordPress from the very beginning and uses less disk space for cache files because it saves only useful information. It saves information separately and also caches hidden requests to database. Dmitry Svarytsevych analysed server load graphs of his sites and he can say that the peaks of server load are caused of search engines bots indexing your site (they load much pages practically in one moment). He has tried WP Super Cache to decrease the server loads but it was no help from it. Simply saying WP Super Cache saves any loaded page and much of these pages that are opened only once by bots. His original plugin (DB Cache) roughly saves parts of web-page (configuration, widgets, comments, content) separately, which means that once configuration is cached it will be loaded on every page. Here is the Google translation of Dmitry Svarytsevych's article on it. Troubleshooting Make sure wp-content is writeable by the web server. If not you'll need to chmod wp-content folder for writing.

Disable it at Settings->DB Cache Reloaded page. The plugin will automatically delete all cache files. If something went wrong - delete /wp-content/db.php, /wp-content/db-config.ini and /wp-content/tmp folder manually. When wp-content/db.php file exists, WordPress will use our optimised DB class instead of its own. Deactivate it at plugins page.

By default DB Cache Reloaded shows number of cached queries in hidden HTML comment in page footer. When you see -1 as a cached queries count, this means that caching is not active. Please make sure that you have enabled caching on settings page (DB Cache Reloaded also shows message in admin backend when caching is not enabled). If caching is enabled and you still see -1, this is a result of conflict with other plugin, which wants to replace default wpdb class with its own too. You have to disable plugins one by one until you find one which causes this conflict. If you have added custom code to your wp-config.php (or other file) in order to install plugin, please remove (or comment out) it too. When you find conflicting plugin, please notify its author about this problem. You can also try to enable Wrapper Mode - it may help.

Please check if you have enabled caching. If yes, this may indicate some problems with your plugins - check previous question (Why plugin shows -1 as number of cached queries?) for more details.

When DB Cache Reloaded works in Wrapper Mode, it uses different method to load DB Module. By default plugin assumes that WordPress will be able to load wp-content/db.php. However sometimes other plugin may load wp-includes/wp-db.php file directly, or replace value of $wpdb variable. This usually does not allow DB Cache Reloaded to work. When you enable Wrapper Mode, DB Cache Reloaded will load a bit different DB Module, which adds caching and works as a proxy for DB Module loaded by other plugin. Depending on your plugin, everything may work smoothly, or there may be some issues. Wrapper is also a bit slower then normal method, and does not cache all queries (usually one, but some plugins may increase this number). It also requires at least PHP 5 to work.

DB Cache Reloaded uses default WordPress mechanism to load custom version of wpdb class - it creates custom wp-content/db.php file. WordPress checks if this file exists, and loads it instead of wp-includes/wp-db.php.