While w3 Total Cache is one of the Best Caching Solutions for WordPress, It has it’s own side effects.If you are using W3 Total Cache, then some configurations you set may lead to suspending your Hosting Account by your Hosting Provider.I’m not sure why the developers have put efforts to fix this issue with W3Total Cache.
I haven’t noticed this issue until the hosting account used by this website is suspended by bluehost for violating their TOS, after investigating I found the culprit is W3 Total Cache.
It may be BlueHost, Hostgator, Ipage, HostMonster or Godaddy, any hosting provider will suspend your hosting account if you cross the file limit given by them & after that there are less chances for you to recover from that.
Main reason behind this is W3 TC (Also tested on latest version) creates thousands of inodes a day.If you want to check go to Object Cache Folder & you can notice large number of directories and files under the folder, the bad thing here is these files doesn’t not get deleted even on clearing all caches.
Workaround : If you want to still use W3TotalCache but don’t want to get your Account suspended then I would suggest you to disable DB & Object Caching Mechanism.These modules are the main culprits in W3TotalCahce which create a lot of I/O on the server.
If you are on a shared Hosting server with very few accounts, then it’s ok to enable DB and Object cache, but remember one thing on shared hosting, it ends up being slower to access the caches from disk than it would be to just do the database query in the first place.
If you do have a VPS or Dedicated server, then you are probably not sharing your server with several hundred other people, so DB and Object cache may really improve your site’s performance. This is especially true if you enable eAccelerator or APC and/or set up Memcached.
Had you faced Hosting account Suspension because of w3 Total Cache or some other plugin! Please share with us so that it can be helpful for others to avoid some common mistakes.