Few questions for clarification

  • Resolved iamonlythird

    (@iamonlythird)


    3 years ago

    This plugin has a lot of potential and I am planning on implementing it on tons of my clients platforms. However can you please answer these questions:

    1. Your description on “is my cache working” is a bit unclear. For example, what exactly should one look for in the Site Health screen to see if caching is properly enabled?

    You mention opening the site on incognito mode (to see a fresh logged-out version of the page). But how exactly can I see if the caching is enabled? Looking at the source but no comment is added at the end.

    2. When exactly are cached pages generated? For example, will it auto-generate cached pages (preload as it’s called), or will the cached page generate when it is visited for the first time (since it was flushed)?

    3. How often is the cache flushed? What triggers it? Is it when a new post is created? If so, when I add this on a platform that publishes a new post every minute, then it wouldn’t fit, right?

    4. Does it do anything else besides page caching? Such as browser caching etc? I can see that no minification of files are being made (not that it’s a requirement, just curious).

    I think this plugin has a lot of potential as who has the time and interest to spend a week reading outdated guides on which bizarre settings are appropriate for W3 Total Cache etc. I can see this being one of the most used caching plugins in the future. But I feel the information will need to at least be present so that people know what they are signing up for! =)

    Thanks!

Viewing 1 replies (of 1 total)
  • Plugin Author Konstantin Kovshenin

    (@kovshenin)

    Thanks for trying out Surge @iamonlythird!

    1. You will see a green “Page caching is enabled” under a “Performance” label in Site Health when everything is okay, or a yellow/red label with an explanation of the problem if there is one. You can also verify that cache is working correctly by inspecting the X-Cache header in the HTTP response.

    2. There is no preloading. Cache is generated only on demand when a user first visits a page.

    3. The default cache lifetime is 10 minutes, after which the cached entry is invalidated. Creating a new post, updating existing posts, adding widgets, changing menus, some settings etc., all trigger invalidations for various cache entries.

    4. Surge does page caching only.

    Hope that helps and let me know if you have any other questions!

Viewing 1 replies (of 1 total)
  • The topic ‘Few questions for clarification’ is closed to new replies.