well congrats on having a lot of traffic!
The number of resets indicates that something is making database changes – which could be a plugin that is doing logging or something. So in that case, you can look for something to possibly tell NLC to ignore that by not resetting the cache. To do that you need to do a little detective work. On the settings page there will be a line that says “Last Reset Query” which will show you the query that caused the most recent reset. If you can pick out something unique from that like a plugin name prefix or something then you can add it to the “whitelist”. There are some instructions on the settings page for how to add to the whitelist.
The prunes on the other hand mean that the cache is filling up and NLC is clearing out space to make room for more items. You could try going to the db.php file and editing the static variable $MAX_CACHE_SIZE to something larger and see if that helps reduce the number of prunes.
The prunes are more of a concern than the resets because they indicate the cache isn’t big enough to hold all of the content. But, it might still be OK just since you have a good amount of traffic coming through that a high number of prunes is natural. I would experiment with that setting and see if you can find a good number that reduces prunes without making the cache so big that it takes too long to load it.
Thanks for giving the plugin a try and please let me know how this goes..?!
