Title: Setup Wizard – different results
Last modified: July 20, 2023

---

# Setup Wizard – different results

 *  Resolved [Castor](https://wordpress.org/support/users/castoruk/)
 * (@castoruk)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/setup-wizard-different-results/)
 * Hi
 * Sorry if this has been covered before.
 * Im using the plugin on a server which has Memcached enabled.
 * When I use the setup wizard, and I often get different speeds on the Database
   and Object cache screens. Keep pressing the Test button comes back with different
   speeds each time. Sometimes disk and/or memcached quicker than None, sometimes
   they are not. Sometimes it’s just by a percentage of two, while other times it
   can be in the 10s or 20s.
 * I’m aware the speeds won’t be exactly the same each time, but it varies so much.
 * Is there a hard and fast rule when it comes to these settings? If Memcached is
   available should it always be enabled for DB and Object caching for instance?
 * Thanka for any advice.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/setup-wizard-different-results/#post-16910240)
 * Hello [@castoruk](https://wordpress.org/support/users/castoruk/)
 * Thank you for reaching out and I am happy to assist you with this.
 * As a general rule, it’s not recommended to use DB caching and Object Caching 
   to Disk. 
   Disk-based caching is not that efficient. In other words, it’s recommended
   not to use database caching with it
 * Moreover, using disk-database caching can make your site slower. This is so because
   getting data from the database can be faster than getting cached data from the
   disk.
   If you know that database is the bottleneck of your website performance,
   then Object Cache (like Database Cache) is beneficial to use. But in this case,
   it’s recommended to use Opcode, Memcached, or Redis options (Memcached in your
   case)
 * I hope this helps!
 * Thanks!
 *  Thread Starter [Castor](https://wordpress.org/support/users/castoruk/)
 * (@castoruk)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/setup-wizard-different-results/#post-16917633)
 * > Thanks for replying.
   > I wasn’t thinking on using disk caching for these. My question was is there
   > a reason why the memcached speed results could display as slower and faster
   > randomly?
   > And should I use memcached anyway, even if it shows slower?
 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/setup-wizard-different-results/#post-16918297)
 * Hello [@castoruk](https://wordpress.org/support/users/castoruk/)
 * If the database is the bottleneck of your website performance you should use 
   Memcached. Disk is never recommended. So the answer is yes, and the testing results
   may wary depending on the server resources and the resources allocated to memcached.
 * Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Setup Wizard – different results’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

## Tags

 * [object](https://wordpress.org/support/topic-tag/object/)

 * 3 replies
 * 2 participants
 * Last reply from: [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * Last activity: [2 years, 9 months ago](https://wordpress.org/support/topic/setup-wizard-different-results/#post-16918297)
 * Status: resolved