W3 Total Cache inodes – file usage
-
I am a dummy in all this but have had so much help here I want to give back if I can.
Using SUPER CACHE I was getting really bad results from GOOGLE SPEEDTEST but I had a static FILE USAGE at 55K.
I have a cpanel shared server at godaddy with 13k articles in the DB and I am graphic and video heavy.
The day after I switched to TOTAL CACHE I was over 200k in file usage and closing in on the limit.
I found little info about this here and what there was rather old.
I seem to have fixed the problem by NOT enabling DB or OBJECT cache, as soon as I did it cpanel showed FILE USAGE at 30k, though not static and growing. So am not yet sure this is a real fix.
I also do not know if disabling those two areas is a good idea but the PINGDOM and the SPEEDTEST stayed at the same much better level than I had with SUPER CACHE.
What seems to have got me Gooble Speedtest from 59 to 86 was I found that in the MEDIA cache area the default was OFF so the default timeout number was not activated. This is what initially boosted my GOOGLE SPEEDTEST from 59 to 86.
Hope this helped and any added info would be great.
KickerOh, pingdom difference tween cache and no catch is 2.0 seconds with 4 seconds without.
- The topic ‘W3 Total Cache inodes – file usage’ is closed to new replies.