Worker mode

  • I’ve been using the plugin for a while in page rule mode. I recorded my page TTFB when login and logoff as following :
    > login TTFB = avg 3-4 sec (with ?swcfpc=1, cf-cache-status : BYPASS)
    > logoff TTFB = avg 40ms (cf-cache-status : HIT)

    Now I just tried worker mode and I’m not sure if it works as it should.
    Here is what i did :
    – change to worker mode / save.
    – disable cf cache everything page rule (no active page rule left).
    – test cache in the plugin and it said that page cache is working properly https://i.imgur.com/isthHu6.png
    My TTFB in worker mode is as following :
    > login TTFB = avg 800ms (without ?swcfpc=1, cf-cache-status : DYNAMIC)
    > logoff TTFB = avg 800ms (cf-cache-status : DYNAMIC)

    My question are :
    1. Is this what it should be ? Login TTFB is much better, but logoff TTFB is getting worse and about the same as when login.
    2. Why worker mode logoff TTFB is higher than in page rule mode, I expected the status HIT just like in page rule mode ?

    My URL is https://www.zoomcamera.net/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter naratt

    (@naratt)

    Here is my cloudflare screenshots, FYI:

    View post on imgur.com

    View post on imgur.com

    View post on imgur.com

    Plugin Contributor iSaumya

    (@isaumya)

    Hi as I can see the worker mode is working perfectly fine on your website. When using the worker mode the 1st request will be a cache miss which will show off as DYNAMIC but after that it will be cache HIT.

    If you check the response header you will see a new header x-wp-cf-super-cache-worker-status with the status of the cache.

    Also when using the worker mode you don’t need to use the cache buster query string ?swcfpc=1.

    Thread Starter naratt

    (@naratt)

    As per my test , for the main document :
    cf-cache-status: DYNAMIC
    x-wp-cf-super-cache-worker-status: bypass .
    no matter log on and log off.
    Log on > https://i.imgur.com/nSbYFjG.png https://i.imgur.com/d1ce2TO.png
    Log off > https://i.imgur.com/J9B7V8U.png

    I also found that other files are :
    cf-cache-status: HIT
    x-wp-cf-super-cache-worker-status: hit.
    for both Log on and Log off > https://i.imgur.com/SMjzNNi.png

    1. How do you check, please provide video/screenshots ?
    2. If working properly, should the TTFB when log off be a lot faster than when log on ?
    Please answer my questions respectively.

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @naratt,
    I think you did not checked the response header correctly as it already have the answer you are looking for. When x-wp-cf-super-cache-worker-status: bypass there is also another header that is x-wp-cf-super-cache-worker-bypass-reason which shows why the page is being bypassed. So, in your case as I can see it is happening because of an WooCommerce cookie.

    The reason the pages needs to be bypassed for the woocommerce cookies is because those cookie values are used across pages when someone is viewing it. So, if you cache the page and hypothetically ignore the cookie users might face problem like things added to cart but as soon as they go to another page it is not showing up. Or if you have a section for recently viewed items, that won’t work. Cause when a page is served from cache it there is no dynamic element to it (except the javascript-based dynamic stuffs). Hope that helps.

    Thread Starter naratt

    (@naratt)

    Many thanks.
    So in case that the website has woocommerce installed, no matter logon or logoff, the cache will always be bypass, right ?
    Does the worker mode still help website speed as the cache is bypass ?

    I’m wondering why the TTFB is still better than normal mode ?swcfpc=1 even when it’s bypass ?

    Plugin Contributor iSaumya

    (@isaumya)

    So in case that the website has woocommerce installed, no matter logon or logoff, the cache will always be bypass, right ?

    – No. Depends on how WooCommerce is set on the site along with what other woocommerce plugin/extensions are being used and how they are setup. If you are using a system that is not using any woocommerce_ cookie and rather use javascript localStorage or Ajax to do things then those pages can be cached.

    As I said before you don’t need ?swcfpc=1 cache buster query parameter when using the worker mode. It is only used when you are using the default page rule mode.

    Thread Starter naratt

    (@naratt)

    I know that ?swcfpc=1 is not needed in worker mode. I just wonder why the TTFB is much longer (about 3 sec) when using traditional mode (with cache buster) than when in worker mode (about 800ms in dynamic.

    Moreover, after using worker mode for a couple days, we found some users reported that they see other user’s data (I assume it’s from cache). How can we solve this ?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Worker mode’ is closed to new replies.