Static Requests are super cheap to Cloudflare and get even cheaper the more cache gets hit
Static Requests are super cheap to Cloudflare and get even cheaper the more cache gets hit
IHow do you propose tracking that, though? Imagine if 32 users (Starlink) share an IP, and they hit 404s. If you block that IP you might be blocking 1 bad user but 31 good users who hit a 404.
CIt'd most likely be more compute intensive to try to store/do all that, then just serve the static requests
Ccool down period?
CDoing all that across tons of machines is a ton of cost of sync, and a ton of code to go wrong, etc
Cat some point workers-and-pages-discussions
CAny anti abuse stuff like that can go wrong too and block legit use cases, just not worth it
Cbecause cloudflare has so much traffic going through it..at some point its the only answer to crush the bot delema that soaks up so much computer and bandwith on the internet
CDenial of service attacks only exists because there is no communication or effort amongst hosts to do anything
Conly cloudlfare has the ability to centralize an effort
CBandwidth is pretty cheap to CF in most cases with their vast network, and compute is more expensive to do anti-bot stuff across thousands of machines then to just serve static assets which can be cached everywhere
Cof my VPS servers that run behind cloudflare, 80% of the cpu is just bots going for non existant files
Cand occassionally i'll drop in, block an ASN and then it will be another ASN 1 month later
ISure but at that point it's very user-specific and Cloudflare wouldn't take action to block things on your own domain when it might be blocking things for legitimate users.
Csending any abuse type email is generally never read
IIf you want to reduce that kind of thing you can deploy your own rules that are tailored to your specific domain
II.e rate limiting rules.
Ci mean i do it for my domains already, i'm suggesting something just for pages.dev, but also my 2ndary conversation is the concept of cloudflare being the hub to lower bot traffic in the world in some way. It would be a form of community service in line with how it pushed back against patent trolls.
Cjust an idea
Canyways...carry on
Cnow getting a ton of 404's for /sito/wp-includes/wlwmanifest.xml I HATE BOTS...just flooding me.
Si get thousand of bot requests a day :Shrug:
Swe are smart and dont put credentials or anything on the client tho so we are fine
Sgod i love how many services cf offers i have to hold back to not implement everything for simple apps 
but maybe rate limiting.. just 1 more
but maybe rate limiting.. just 1 more
1Is there somewhere I can track the changes to CF docs?
C
GitHub
Cloudflare’s documentation. Contribute to cloudflare/cloudflare-docs development by creating an account on GitHub.
1Thank you wasnt sure of the exact repo
1This was the change I was trying to figure out manually 
no wonder I couldnt find it lol
no wonder I couldnt find it lol
Si updated some lib and now i get that build error even tho im using
and yes
"compatibility_flags": ["nodejs_als"] any clues why this would error now?and yes
nodejs_compat
Scould this be a change from
node:async_hooks to just async_hooks ?
KDoes hyperdrive cache queries that return 0 rows?
M#hyperdrive
MAm I right that
...will I see "hi!" in the console 5 seconds after the worker has sent a response? (And presumably I don't need to use
waitUntil() can be used to ensure an asynchronous process will complete even after a response is sent? So if my worker has this:...will I see "hi!" in the console 5 seconds after the worker has sent a response? (And presumably I don't need to use
await
MIf I'm getting build errors for workers where the only error in the build log is "
Failed: error occurred while updating repository submodules" is there any way to get more information about the error? I've exhausted my ability to troubleshoot past this.
Phmmm i have an issue that cloudflare/pages-action@v1 still uses node 20 - but it seems i need node 23 to deploy the latest nuxt to it. Is the pages-action outdated? or will there be an update for it?
SAnyone know why there is suddenly a 1,000 worker route limit per account?
SI have more than 1,000 but users are now reporting this error.
SThere is nothing documented about it, and I can't even tell if the Business plan ups the limit.
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.THi, does anyone knows how CPU is shared between isolates (workers) ?
I am running an LZ based compression algo in Rust compiled to WASM.
For the same file compressed I see high discrepancies in CPU time: most of the time it consumes about 1500ms of CPU time but sometime 2500 or 3000ms.
The worker is just calling that wasm instance, no I/O calls.
So it seems vCPU allocated to an isolate is not fixed. This seems unfair as we are billed by CPU time and sometimes we can be billed 2x,3x for the exact same compute (no I/O involved) depending on the vCPU allocated to our isolate.
Plus the fact that it adds latency to get the response, so we pay more for slower execution..
I am running an LZ based compression algo in Rust compiled to WASM.
For the same file compressed I see high discrepancies in CPU time: most of the time it consumes about 1500ms of CPU time but sometime 2500 or 3000ms.
The worker is just calling that wasm instance, no I/O calls.
So it seems vCPU allocated to an isolate is not fixed. This seems unfair as we are billed by CPU time and sometimes we can be billed 2x,3x for the exact same compute (no I/O involved) depending on the vCPU allocated to our isolate.
Plus the fact that it adds latency to get the response, so we pay more for slower execution..
MCF devs may be interested to know that Cursor, the AI assistant, is giving 404 links to the docs. This is because the URLs it outputs are relative, not absolute, yet lack the prefix
/https://developers.cloudflrare.com/workers/ai/. This results in URLs like the below being generated:
SHey guys, I have a problem that my production worker is much slower then staging one even though the only difference is the traffic (the code and configuration is exactly the same). Do you know how can I fix it?
Kfeels like that is something that would be easier done external? :D
Klike a server that is set up for compression - lz compiled with cpu flags and then its probably 10ms, you could transfer the data from worker to worker and compress in way less time then
IBy definition CPU time is invariant of number of vCPUs. Even if two cores are allocated/working at the same time then there will be the same number of CPU (milli)seconds... but that can't happen in Workers because they're single-threaded anyway. Not sure what the reason for the variance you're seeing there is. How are you getting the specific CPU time metrics? GraphQL API?
TThat what I currently do, those CPU heavy algos are running from GCP cloud run with allocated CPU. Waiting for cloudflare containers to see what they have to offer
Kyeah id def outsource that part, workers always seems more of a platform for <100ms tasks :D
TThat is what i thought also, as CPU time should be invariant of vCPU allocation. But for those algos I see wide CPU time variations, seen from workers logs (beta) in CF dashboard.
AHello. Looking to understand a little more about the lifecycle of a durable object. In the constructor of the durable object class, I want to create a store and then add a listener to it. What I'm trying to figure out is how to properly clean up the listener. It's my understanding that if the do hibernates and wakes back up, it will run the constructor again. Do I need to worry about removing that listener? Is there a method I can override to include code to remove the listener? Thanks in advance.
IWhen a durable object hibernates, all memory is cleared. So in your case the store would vanish completely (and so it's fine to reattach listeners). Anything you want to persist across hibernations should be put in the DO persistent storage, either via the classic KV API or the new SQLite API.
AGreat. Thank you.
