Cloudflare Workers KV usage

  • Resolved paktas

    (@paktas)


    2 weeks, 2 days ago

    Dear plugin team,

    Cloudflare recently announced making their Workers KV x3 faster.

    I have read your other support forum posts, where you suggest NOT to enable Workers for your Super Page Cache plugin.

    We are using APO (on business plan), but it’s clumsy, HIT ratios stuck ~90%, HTML’s getting MISSED or even BYPASS and we don’t have full controll over cache clearing (ex. to leave static untouched).

    We are evaluating option to migrate to your plugin, but you do not recommend Workers… which CF says are x3 faster now.

    Can you clarify if:

    1. Using you plugin with Workers KV is an option?
    2. Using your plugin with default page rule caching still has advantages over KV option?

    We are having:

    • Monthly ~2M visits & 250M requests
    • Bandwidth Saved: ~90%
    • Cache HIT ratio: ~94% (mainly statics – CSS, JS, img)
    • Tiered cache -> Cached Origins: ~43% hit ratio (just enabled Smart Tiered Caching Topology)
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    This plugin does not uses worker or worker KV instead it leverages Cloudflare Cache Rules.

    Thread Starter paktas

    (@paktas)

    You wrote on this forum that Workers mode is to be removed and not needed.

    Could you clarify on why Workers are “not needed”?

    As per above – seems Cloudflare is heavilly investing in speeding Workers KV to the limits.

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