Durable objects also charge for the in memory cached reads which is odd too <:NotLikeThis:9469502227
Durable objects also charge for the in memory cached reads which is odd too 
DComing from this model originally I believe is fine, as a next step it would be very Cloudflare (ahem, 0-egress 
, end billing when stream response returned, etc) to now say ok, cached reads are now free
, end billing when stream response returned, etc) to now say ok, cached reads are now free
DI didn't even think about DOs, that's another good one - that would eliminate another 
lru-cache (https://www.npmjs.com/package/lru-cache) usage 
HThe issue with building your own cache on top of DO storage is that you don’t have a real easy way of measuring memory usage, where iirc the default in-memory cache auto-evicts when memory is low
Dlru-cache can (sort of) deal with that, for ~100 keys that shouldn't be an issue even if all keys are 128KB, but most (at least for me) are under 2KB
BYeah. The team is aware of the DO thing. That being said, most providers will do caching underneath of any storage product and eat the savings so it's not rare and I don't think it would change for DO. I wouldn't recommend putting Cache in front of DO because you have no way of guaranteeing the consistency of the contents in cache / DO. lru-cache is a cute idea and would work now but I suspect it'll not be sustainable as DO matures over the years for more than toy examples (although I could be wrong).
Maybe the main actual weirdness is that the Cache API is free. I'll see about making sure we start charging for it. Be right back. Will flip the flag for that.
Maybe the main actual weirdness is that the Cache API is free. I'll see about making sure we start charging for it. Be right back. Will flip the flag for that.
UI think the only reason people complain about charged cache reads on CF is the fact that the cache api is free tbh
HWhat have you done, Dani?! YOU’VE DOOMED US ALL!!!
UDoesnt totally make sense in peoples minds that cache api is free but cached database reads are not free
HEspecially if there isn’t a whole lot of extra logic that goes into the cache. For example, you could probably charge a little bit for SWR caching on KV, but maybe not as much as a full read
HThe auto-pull while cached thing is a feature on top of what the Cache API offers, which is why I think you could justify at least a slight cost there
DWe've actually agreed with @beelzabub in DMs that I'd get 1% of all Cache API bills 
HI’ll be fine with that arrangement if you pay the Cache bills for everyone, not just yourself
DLook at us complaining about products priced at $0-5/million range compared to saas's which build on these and charge you $40-50/user/month
HI mean, I don’t think I can complain at all… :winks_in_green_cloud:
Dalso you're a champ, you have a free ent account, 
D(I'll pay yours of course)
HDisables NoCost just for funzies
DI know this is getting sortof #off-topic, but I no longer superlike you, mr superchamp
BMonkey paw wish granted. Everyone gets a 1% coupon thanks to @Dani Foldi volunteering to cover 1% of everyone's bill.
BThey count. But note it's per request. Not sure why you'd make repeated KV reads within the context of a single request
Dsudo rm -rf nooo how else do I stop thisBI thought https://protomaps.com/blog/serverless-maps-now-open-source was interesting.
A web application with 50,000 map loads using the Google Maps API will cost $350 per month.
A similar amount of traffic running through a Protomaps CDN install on Cloudflare, with an average of 20 tiles per session, costs fifty cents in Cloudflare Workers request fees.
B@_john_n does that answer your question? I'm kind of curious about the context where you're concerned about the 1k limit
HIf you want to see an (admittedly bad) implementation of that, you can try https://maps.goalastair.com
HIs there an easy way to cache Range Requests? Then I could maybe speed it up a little...
BI thought range requests are generally cacheable, no? You might need to store the actual asset in cache once but after that cache.match will honor ranges? I forget the details though. CDN behavior is extremely complex and I don't pretend to know it outside of the specific slice of how I'm using it
HI don't think so? I tried tailing the Function, and I'm getting
Kput will want the full file but you can make ranged reads against matchKSame-ish behaviour as the normal CDN, except that all happens transparently (it'll pull the full file and serve you the range, then serving other ranged reads from that full file)
HOk, so there goes my idea. No way am I going to be able to
put a 60 GB file in every requested colo…KYou could probably hack around it, emphasis on hack.
Kput just doesn't like the status code of 206 - but if you store a ranged response w/ a body of 200 then you'll be matching any ranged read against that unless you store the requested range as apart of the cache key.KI don't think you'd gain very much in exchange for a very cursed caching method though
HI’m trying to get their Worker example working, which does the Range requests on the Worker side. Should be a little less of a pain…
BDoing 1000 subrequests within the context of 1 request is going to be slow (like ~1.6s to actually make if it's all cache hits) and feels like a lot. Are you sure you're doing 1k or more subrequests within the context of a single incoming request?
BInstead of storing each IATA code as a separate value, have you considered just storing it as 1 giant bundle and just caching the data on first use? I imagine the data doesn't change and it's probably quite small right?
BSomething like:
BWhether or not that works depends on the size of the data of course. If the object size is closer to ~100 MiB, you might need to start chunking somehow (e.g.
iata-AtoD.json, iata-DtoH.json, etc)BI figured. I had a IATA lookup table in a recent project I was playing around with and I think the entire website was just over 1 MiB compressed. Would have bundled it directly into my worker to simplify things but I don't know if >1 MiB workers are supported yet
U5 MiB paid plan 
BGrrrr. Should have just tried it. That's what happens when you rely on information from 2 years ago. I actually helped plan the work needed to raise that limit. I just rolled off to start R2 before that work completed and I did a bad job of following up. Good to hear it's been raised
KHi team - is it possible to do a list operation on a KV and have it stop at a certain character? E.g. I have these entries
1 - key1/keyA
2 - key1/keyA/keyAA
3 - key1/keyA/keyAA/keyAAA
and I just want to list and get 1 and 2 but not 3
1 - key1/keyA
2 - key1/keyA/keyAA
3 - key1/keyA/keyAA/keyAAA
and I just want to list and get 1 and 2 but not 3
Jnot to my knowledge
Kyeah kind of tricky trying to get a graph type situation going on using KV alone
BI do want to get to make list operations more like R2, but I'm not sure we'll be able to do that this year.
