Support » Plugin: SG Optimizer » A few questions

  • Resolved gbruzzo

    (@gbruzzo)


    Hello there!

    after tinkering with your plugin, a few questions came to mind.

    1. How often does the plugin autopurge the cache? (does it at all?)

    2. How does the plugin autocache? Does it spider onto the sitemap? (dont’ thinks so, but curious)

    3. First visit can be a little slow: visiting the (test) site for the first time after a while (say a night with very few visists, if at all) causes the first visit to take considerably longer (several seconds in our case vs sub/around 1sec). Successive visits/tests are considerably faster (sub 1sec/around 1sec). Why is it and what can one do to reduce this?

    4. your minification / concatenation algorithms for js and css are very ‘gentle’ – while I understand that with Http2 having 80 calls or 140 calls does not really matter, I wonder what your plans for improvement are. Have you considered using this compressor to further enhance your product? https://github.com/wpsharks/html-compressor. It’s the best / most efficient I have ever used. Alternatively, it would be lovely to truly integrate a plugin like Fast Velocity Minify or Autoptimize into SG Optimizer (one dashboard / interface for everything). Working with two plugins can be complicated (multiple caches to correlate etc) and create more hassle than is worth.

    5. It would be very useful to be able to switch static cache off from sg optimizer as well. I gather Memcache should stay on, as different installations might be accessing the same memory pool

    That is all for now, thank you very much.

    Giacomo Bruzzo

    • This topic was modified 2 months, 1 week ago by  gbruzzo.
    • This topic was modified 2 months, 1 week ago by  gbruzzo.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    Hey,

    Let me address your questions one by one so I don’t miss anything.

    1. The cache purges it depending on the server’s configuration depending on your site usage. Different parts of the cache are automatically updated by Nginx if they are not accessed for 3 hours or more.

    2. The plugin monitors core hooks and purges the cache accordingly. When you modify your content, different parts, or the entire cache is flushed.

    3. First visit is dynamic which means it’s as fast as your site is developed to be without a caching mechanism to turn it basically into a static html. I would recommend switching to PHP 7.3 and do pre-cache optimizations in order to get fast first hits.

    4. Yes, because there are a lot of plugins and themes that do things far away from the coding standards and if we’re less gentle, the plugin will start breaking functionality. There’s a new Combine CSS toggle that will help you reduce the number of requests. If you want’ you can use another minification service, that’s not a problem, simply disable it on the Optimizer’s end to avoid duplicate functionality.

    5. The Dynamic Caching cannot work without the static cache. As to the Memcached pool – only applications from your account can access it since we spin off new instance for each cPanel account πŸ™‚

    gbruzzo

    (@gbruzzo)

    Thanks for your answer

    “3. First visit is dynamic which means it’s as fast as your site is developed to be without a caching mechanism to turn it basically into a static html. I would recommend switching to PHP 7.3 and do pre-cache optimizations in order to get fast first hits.”

    please clarify – are you talking about opcache.preload? that will only appear on 7.4 though?

    “4.” That is what I thought. My comment was a suggestion for you to look at a (maybe better) implementation of html/js/css minification/concatenation, as implemented by CometCache

    “5.” All Clear : my question was more : it would be nice if one could switch the static/dynamic/memcached caches on/off via the plugin itself (instead of having to log onto Cpanel and do it manually). The plugin allows the cache to be flushed, but not switched on/off (it does for dynamic, but not for static and not for memcached, as far as I could observe).

    Cheers

    Giacomo

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    I am not talking about opcache.preload but our dynamic cache which is powered by an NGINX reverse proxy. If you get a dynamic hit (not cached) then you want to have the fastest available PHP to handle it. If not cached hits are very slow, that points to problems with the site architecture which caching only masquerades.

    We constantly update and improve our optimizations, doubt that other plugins are doing something better, honestly. We will soon introduce an interface update with even more optimization options.

    5 – totally. We’re doing that but that requires an update of our service structure which takes more time. Hopefully in few months you will see some great new things in that direction too πŸ™‚

    Hello there, thanks for your answers, they help clarify. Sorry for asking so many questions, but I would like to understand how the plugin works best I can. I need to be sure of the oil I put in my engine, if you will.

    Therefore, here I am again:
    How does SG Optimizer auto-cache?

    – does it autocache the first time settings are set?
    – does it autocache everytime cache is purged (I assume this means static, dynamic and memcache are being purged)?
    – if it does autocache, what map of the site does it use? there is no reference to a sitemap that I can see?
    – does it autocache on cron (I can only see one monthly delete cron event, so I suspect not).

    What I know/think I know:

    – Any page or post (custom or otherwise) not accessed for more than three hours is automatically recached (great).

    thank you for any light you can shed.

    Giacomo

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.