WordPress.org

Support

Support » Plugins and Hacks » [Plugin: DB Cache Reloaded] Idea: Don’t cache queries that were fast enough

[Plugin: DB Cache Reloaded] Idea: Don’t cache queries that were fast enough

Viewing 4 replies - 1 through 4 (of 4 total)
  • I agree with you. I will look on it to see how this can be improved.

    I also think of option to get the real-life numbers – the optimum threshold will vary from server to server.

    Thanks. If you decide to get the real-life numbers, remember to remind the blog admin to measure benchmarks during the web server and/or database server’s busiest hours, that is, the time the plugin can help the most.

    Hi again,

    I tried doing this on my own, by replacing two lines in db.php from:

    $dbc_cached = serialize($dbc_cached);
    $dbc->save($dbc_cached, $dbc_queryid); }elseif($dbc_cachable) {

    to:

    if ($this->timer_stop() > 0.0001) {
    		$dbc_cached = serialize($dbc_cached);
    		$dbc->save($dbc_cached, $dbc_queryid);
    	}
    }elseif($dbc_cachable) {

    (SAVEQUERIES was defined earlier.)

    After much trial and error during my servers’ busiest hours yesterday, I came to the conclusion that, at present, DB Cache doesn’t help me at all. On a typical blog page of mine, during heavy traffic, running the original queries was always faster than retrieving the results from the filesystem.

    I’m writing you back right now because (a) benchmarks could show that DB Cache won’t help a blog, and (b) I suggested the idea in the first place.

    Thanks for sharing these results. It looks that plugin requires another cashing option – e.g. in memory.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: DB Cache Reloaded] Idea: Don’t cache queries that were fast enough’ is closed to new replies.
Skip to toolbar