11 thoughts on “Autoptimize cache size: the canary in the coal mine”

1. Mike Irish 23 September 2016 at 20:18

   Thank You!!!
   Finally I think I understand more about the “caftty-cascheing” in AO.
   Your…. canary in the coal mine….allagory seems perfect to me!!

   Thanks so much…from a longtime user!

   Reply ↓
2. /hauke 29 September 2016 at 11:04

   Hi,
   firt of all, thank you for providing autoptimize!
   I don’t mind that ther cache grows big – however, the blinking red circle annoys my editor-in-chief :-)
   Is there any way to set the threshold where it starts to blink? e.g., 10 GB or whatever?

   Thank you,
   Hauke

   Reply ↓
   1. frank Post author29 September 2016 at 11:20

      sure, using the API;
      add_filter('autoptimize_filter_cachecheck_maxsize','change_maxsize');
function change_maxsize() {
return 10*1024*1024;
}

      Reply ↓
      1. /hauke 29 September 2016 at 11:24

         Wow, that was one fast reply! ;)
         Since I’m not really into wordpress-hacking – which of the many php scripts should this be placed in? Preferably something that does not get overwritten the next time I update either wp itself, your plugin or my theme – is there any such thing?
         (And, here’s the feature request: how about making the sizeconfigurable in settings?)

         Thx,

         /hauke
      2. frank Post author29 September 2016 at 11:53

         I have too many settings already, don’t want to add to that, but easiest way to add the code is using the code snippets plugin. :)
3. /hauke 30 September 2016 at 14:28

   Uh, that’s one great tip to use that code snippet thingie, thank you very much – works like a charme!
   By the way, in order to achieve a 10 GB cache size you would have to set 10 * 1024 * 1024 * 1024 – you are using bytes, not kilobytes :).
   I’m trying 1 GB, and for now that seems to be ok. In your opinion, is a cache size of ~750 MB too big? I know that it probably depends on roughly a milion factors – I’m just curious why it is as “big” as it is. So far it’s not really a problem, but I’m wondering: Is my canary about to die?

   Thanks again,

   /hauke

   Reply ↓
   1. frank Post author2 October 2016 at 16:45

      well, 750MB does mean you’ve got a lot of different JS-files, which means that (assuming you have on average half a MB per JS-file) at least 1500 visitors had to wait for the JS-file to be created. I would try to find a way for more reuse of the cached files if I were you.

      Reply ↓
4. /hauke 30 September 2016 at 14:31

   PS: This is what I just got from my “editor in chief” after I applied your “fix”:
   Jaaaaa, DANKE! ❤ :* :* (Yesssss, THANK YOU!)

   So, now you know it was worth the time (at least for me ;-)

   Reply ↓
5. Tom Townsend 19 November 2016 at 01:43

   Is there a way to modify the email so that my client does not get it but I do ? I am an admin on the account but this is a fortune company and their IT is the default admin unless a plugin has an alternate way to pick the admin for the email.

   Thanks

   Reply ↓
   1. frank Post author19 November 2016 at 07:37

      you can use the autoptimize_filter_cachecheck_mailto filter Tom.

      Reply ↓
6. Nuno Morais Sarmento 31 August 2018 at 15:50

   Thank you very much for making this plugin available. Awesome work to make this free to everyone. Thank you

   Reply ↓

This site uses Akismet to reduce spam. Learn how your comment data is processed.