No, because whether or not it is cached, a read from KV itself is always billed.
No, because whether or not it is cached, a read from KV itself is always billed.
HI'll push a change to the defaults when I get time
Bcache api is not involved anymore or what? wasnt the point of the cache api to reduce kv reads ?
HI meant that, the logic that determines whether to read from KV is the same no matter the TTL you set for KV
HSo even if I set it to 60 seconds rather than a year, I would still have the same number of billable requests
Bthats for actual kv reads, but with cache api being with a high cache ttl, shouldnt it avoid kv reads to begin with?
HBy default it is set to 55 seconds, at least at the moment, if that is what you mean
HThough the revalidation logic means that it increases in likelihood the closer it gets to the limit
B50 *
HThis comment is wrong then... Oops
HGot some more stuff to clean up I guess
ADoes anyone to how to go about load testing workers? Is there a way to cap the amount of workers that runs so I can get a rough estimate of max req/s per worker?
Bi dont think there's a cap on that, the only bottleneck can be external I/O that you might be doing, like your database for example
AWe know the DB is fine, we're just shifting our traffic to be fronted by a worker to act as a router. It would be initially about ~60k req/sec? What I'm trying to figure out if every region should be able to handle the work evenly because I'd imagine not every colo has the same amount of servers.
B@HardlyWorkin' cant you just invalidate the cache globally by calling purge on a specific url ?
Bi think any kind of load should be fine
BBWorkers automatically scale onto thousands of Cloudflare global network servers around the world. There is no general limit to the number of requests per second Workers can handle.
VAre there any limits on how many route triggers can one worker have?
VAre you sure?
VSo basically if i would need to run 2k routes i would need to create a duplicated worker with a batch of other 1k routes? Then i would have 2 workers with different batches
VOr are routes tied to all workers on one zone?
Vdo you have experience in raising this limit? I see there is an option to " use Workers for Platforms or request an increase to this limit".
VYes i know but i am asking if anyone has experience with raising the limit. If anyone knows costs associated with raising this limit it would be greatly appreciated.
VWe are starting to implement edge SEO via workers on a pretty large webshop. And we dont want to trigger workers on each url because there are a lot of them. Any recommendations would be greatly appreciated.
KWorkers come from the same IPs as https://www.cloudflare.com/en-gb/ips/
KThe only way to really identify your Workers specifically is the
CF-Worker request headerHYou can add a custom block page with JSON, though don’t remember if that is a specific tier
VI need help with wildcards. How can i trigger urls with pattern
domain/shop/shoes/p/id-213
domain/shop/shirts/p/id-214
domain/shop/jeans/p/id-215
...
I tried it like this
but cloudflare only enables wildcard signs at the start of hostname and end of path. Is there a workaround?
domain/shop/shoes/p/id-213
domain/shop/shirts/p/id-214
domain/shop/jeans/p/id-215
...
I tried it like this
but cloudflare only enables wildcard signs at the start of hostname and end of path. Is there a workaround?
Vthat is really unfortunate this would solve so many issues for me
Ocould you share how you achieved this?
SJust using stream mode and writing it back out to the client who's connected the whole time
Ofor me the client disconnects from the stream every 2 seconds which just breaks the functionality as the messages aren't coming through. just sending SSE from a worker using the technique here https://github.com/moishinetzer/remix-live-loader
KYou have to bundle it somehow.
KWrangler uses esbuild, so you could use that directly if you wanted
DI have a question respect the workers + pages product. Shall I throw it here or in what channel?
DI think it's #functions since it's page functions
QHeya, is there a way to run multiple workers locally under the same port? We have a lot of workers and were using miniflare v2. trying to upgrade to latest wrangler, but can't find a proper way to run
CThere's a good explaination of how the cpu limits work here: How are CPU limits enforced in the free tier?
CTLDR being: You have too little requests right now for it to constantly be killing it, but if you get enough requests with that much cpu time, you will quickly run out and hit errors (i.e that's not scalable)
VWhat does this mean "Email Routing can only be enabled when you have a zone on Cloudflare" ?
I have multiple sites and some domain are purchased on Cloudflare itself, so how do i enable email routing? It just keep saying "Add a site"
I have multiple sites and some domain are purchased on Cloudflare itself, so how do i enable email routing? It just keep saying "Add a site"
VHello,
if i have a worker running on a wildcard route.
For example it runs on a whole domain, and then i add another worker that triggers only on one url.
Will they overwrite each other?
if i have a worker running on a wildcard route.
For example it runs on a whole domain, and then i add another worker that triggers only on one url.
Will they overwrite each other?
VMy own domain? Obviously, all my domains are my own.
VThat takes me to Email routes page to create new worker, while I want to bind the
email() routing in my exciting worker
Banyone else getting this error constantly? cant seem to do anything on the dashboard
DIt is not clear which domain you're actually trying with, ... however:
11holidays.com
Does not have any MX record(s), and as such, Email Routing (and any of it's functionality) isn't enabled.dayschedule.uk
Does not have any MX record(s), and as such, Email Routing (and any of it's functionality) isn't enabled.ds7.io
Does not have any MX record(s), and as such, Email Routing (and any of it's functionality) isn't enabled.idm.in
Have MX record(s) pointing directly to Google, meaning that mails will be delivered to Google, and as such, Email Routing (and any of it's functionality) isn't enabled.
DThe error you see, does indeed seem a bit misleading, as the first three domains are zones on Cloudflare, and even using Cloudflare Registrar.
