Those are great questions.
A cache with 182K files is definitely way out of control.
I'm assuming that your site does not actually have 182K pages on it?
I can only think of two reasons why that would happen.
1. If your site is using un-friendly Permalinks, where every URL contains .../?something=something then a bot could hit your site; and tag on session IDs, or other query string variables that would ultimately create 182K variations; out of just a few hundred actual links. ~Not good.
The solution in this case, is to set:
Quick Cache -> GET Requests = True ( Don't Cache )
( that's already the default setting ).
2. If you're using a Custom MD5 Version Salt, that is designed to create multiple variations of the cache, where there is a different variation for every single HTTP_USER_AGENT, as one example... you could end up creating so many different variations, that you'd be instructing Quick Cache to create 1000's of cache files. ~Also, not good. The solution in this case, is to seek assistance from a WP Developer, or a PHP programmer. You should only use a Custom MD5 Version Salt if you know what you're doing.
You'll also want to set a reasonable Expiration Time.
The default Quick Cache setting is 3600 seconds ( 3600 = 1 hour ). It you bumped that up to a year or something outrageous, you could eventually end up with a huge cache directory.Statistics: Posted by Jason Caldwell — July 7th, 2010, 3:08 pm
]]>