• Resolved siki88

    (@siki88)


    Hello,
    I use Litespeed cache and Quic.Cloud CDN. My website is kinda heavy with many plugins and therefore the crawler is really necessary and also doing a great job. But I used vpn to try out some things and read in other, older posts that the crawled pages will be only preloaded on the nearest CDN node. Is this correct? How can I have it preloaded for all CDN nodes? Because my page is heavy then someone from far away will still not receive crawled pages, meaning the experience is slower.

    Also, when it’s not possible to precrawl for all CDN nodes, or only do it through changing the Server IP setting in General Settings to make it preloaded for a specific node, wouldn’t it actually make more sense to use the free option of Quic Cloud with 6 nodes instead of 79? Because 6 Server IP’s I maybe can type in and change manually throughout the day to make it everywhere preloaded, but not 79…

    I hope you can help me. Thanks and best regards.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support qtwrk

    (@qtwrk)

    if your origin server supports LScache , and once page is cached there, it will be essentially like a static request , and connection between origin servers and nodes are usually fast enough , so that only give you very minimal latency between this part

    so best thing you can do for now is crawl on the origin server

    cache sync is on the QC roadmap

    Thread Starter siki88

    (@siki88)

    I use Cloudways as server for my WordPress and QUIC Cloud with Standard (paid) plan for my website. Still when I visit with vpn from other continent for example, the pages get x-qc-cache: miss, even tho all my pages are precrawled in crawler and also get x-qc-cache hit when browsing from VPN here in Germany or normally browsing. What I want is on all nodes also to get a x-qc-cache hit.
    With crawling on origin server, do I have to leave the Server IP on General settings blank or type in my Cloudways server URL?

    Plugin Support qtwrk

    (@qtwrk)

    actually , if the origin is not LiteSpeed webserver, the crawler won’t work there

    are you hitting on same node ?

    Thread Starter siki88

    (@siki88)

    The server is not very far from my location, so it probably uses the same node and it is definitely preloaded for the node here.

    Plugin Support qtwrk

    (@qtwrk)

    please verify by HTTP response header x-qc-pop , there are many factors involved , not only the physical distance , but also latency , network routing …etc

    Thread Starter siki88

    (@siki88)

    When browsing my website in incognito mode, I hit the node:
    x-qc-pop: EU-DE-FKB-67

    How can I know now that it’s the same node that is preloaded?

    I also talked to Quic.Cloud support and they told me this:
    “Crawler can only be utilized to build up a cache layer locally, and unfortunately at this moment it is not possible to pre-warm all the CDN nodes. We will however, plan to launch this feature in future ???“

    Plugin Support qtwrk

    (@qtwrk)

    yeah, locally , in this context, refer to your origin server, but since your origin server is not using LiteSpeed, so crawler just won’t work.

    are you hitting EU-DE-FKB-67 on both cases with and without VPN ?

    Thread Starter siki88

    (@siki88)

    EU-DE-FKB-67 is without VPN and depending on VPN location I hit these nodes:
    New York: NA-US-LGA-33
    Los Angeles: NA-US-LAX-105
    Germany (with VPN): EU-DE-FKB-67
    Netherlands: EU-NL-AMS-357
    France: EU-FR-NTE-51

    Plugin Support qtwrk

    (@qtwrk)

    so , if you visit the page , without VPN , you should hit EU-DE-FKB-67 , and make sure you see cache hit , then engage VPN with DE location , then visit page again , if you hit EU-DE-FKB-67 again , did you see cache hit ?

    Thread Starter siki88

    (@siki88)

    Hi,
    I deactivated the QUIC standard plan to the free plan where I only have 6 nodes. Now I hit without VPN and also with VPN both the node EU-DE-LEJ-613 and I receive cache hit on both.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Crawler and CDN nodes’ is closed to new replies.