It’s stored in KV just like pages stores static assets
It’s stored in KV just like pages stores static assets
Eman
Wsadly we don't have infinite storage on every server haha but trust me, it's very fast regardless.
Eyes but having them be paid is more than worthit. im aiming for atleast 50ms to people nearby
Ealso being able to manually select where you want your replicas to be/stored is also a big +
Eso id want to be in ~300 cities storing 1 MB per city that only comes to 300 MB
Enow ofcourse im not the only user in the world but having this be part of paid workers/pro/enterprise is just so nice
Wwe serve assets much faster than 50 ms today
Wso i'd say you're good either way 
Eehhh from testing it ranged from 10-200ms
Ehow long does cached data stay for?
Wour p95 is less than 50ms haha
Wbut either way, it stays for as long as it can
Wit's lru
E:pepethink:
Eok i didnt know this information
Egood to know
Pinteresting, because my p90 is consistently about 230ms, while it's all hot reads
Punless the
Read latency graph on the KV dash is only for cold reads(?)P
Pohwait you were specifically talking assets KV
Pguess that's different from regular KV
Pstill weird I'm getting those high read latencies when its pretty much all hot reads
Ei didnt use assets kv i used normal kv
Pah hm
P@Walshy | Workers/Pages would you happen to know whether that
Read latency graph is only for cold reads or all? Because if it's also hot reads, then I'm confused as to why the numbers are so highWshould be all yes
P:NotLikeThis:
Wwonder why your p50 is 85ms, that's higher than our p99 :LuL:
Wwant to post in #kv and ping Thomas?
P
Ealso i found that for me it consistently picks different colos for workers
Enot necessarily the closest one to the request
Dhow do i troubleshoot builds that just get stuck at
npm installbuilds timing out at 20min with no errors, just stuck on install, even for a small project with 3 dependencies
DMaybe there is a dependency that tries to run some install script and it gets stuck?
DOr maybe you have a
preparejust by spamming the same worker for requests
Woops yep sorry, misread your message haha
Eall good
EHello
Ewhere can I find the wrangler file for the project in the UI?
LI am using Hono with Cloudflare Workers, when I deploy it the first requests work but the following ones remain pending forever, I look at the logs and only the preflight (OPTIONS) arrives and the request does not continue. Does anyone know what it could be?
JIs there a way to get a kind of one-to-many queue type setup with cloudflare? say I have a "new order" event, and there are various workers that want to react to that. How can I set things up to trigger multiple workers based on an event?
Dperhaps.. but the weird thing is these builds have succeeded in the past, its as if something in our account is borked, which already happened before and @Walshy helped with that. I wonder if its a related issue...
Aim starting to wonder if theres something wrong with my worker now...
My queue consumer worker is stopped at around ~15 seconds of total duration with an outcome of
The docs say that the limit is 30 seconds of cpu time for queue consumers.
AFAIK workers isnt multithreaded, so how is it possible that I am hitting the 30 second cpu time limit in 15 total seconds? This is also with a bunch of network requests, so I doubt all of that 15 seconds is cpu time
My queue consumer worker is stopped at around ~15 seconds of total duration with an outcome of
exceededCpuThe docs say that the limit is 30 seconds of cpu time for queue consumers.
AFAIK workers isnt multithreaded, so how is it possible that I am hitting the 30 second cpu time limit in 15 total seconds? This is also with a bunch of network requests, so I doubt all of that 15 seconds is cpu time
Aoh wait the timestamps on logs arent accurate are they
Aughhhhhh debugging cpu times on cloudflare is a nightmare
Ais it even possibe to figure out what the issue is? literally nothing I do will have accurate times
Athis was all working fine a few days ago, then suddenly almost every execution is failing
Athen it was all fine earlier today, and now its back
