Could the events be grouped in some way? Store groups of events per write request
Could the events be grouped in some way? Store groups of events per write request
LFor $0.25, I wouldn't bother optimizing. Not even for $25. Maybe at $250 if it was simple to implement and manage but containers are generally harder to manage in my experience.
PUnfortunately I don’t control that side. Been asking for that, but they don’t want to do it
PI totally agree, but I’m basically donating the cost to manage this out of pocket currently. I was originally going to just spin up a VPS but figured scale to zero could save a bit (and scale horizontally since I don’t know how many events per month will be happening initially)
PIt’s for managing some stuff for a highschool competition being spun up. Infra is a bit of a mess but until it goes public and gets sponsored basically just doing it for free.
1If it is actually only once a month then you'll stay within the included limits with workers paid anyway
1Doing lots of writes sucks but I wouldnt worry unless your use case would easily push you over included limits
PIt’s once a month per team per event
1ahhh
PAnd I have no clue what the number of teams or events will be
1THat might be an issue lol
PYeah
1What are you doing with the data afterwards?
PIt gets processed into a leaderboard, basically
PHmm. It just occurred to me this could totally be done with WAE
PProbably much simpler
1I wonder if you could store the entire 300k events as a single object in R2 then just process them when you need them via streaming into a Worker?
1or this maybe
PYeah, I’ll probably just use WAE lmao
1300k events for a leaderboard is wild to me, what are you doing exactly lol? If youre allowed to talk a bit more about it
1ahh I see WAE is only 0.25 per mil writes
PHonestly I don’t know a lot of details. Friend came to me and asked for help with the data pipeline. As far as I know it’s some tech related challenge thing, and certain events generate milestones they have to track with some light validation in worker. AFAIK their reasoning for not batching was concern someone would be able to edit it on the computer before the batch is pushed (this seems like something you can design around but I’m not making that part)
1oh and you only get charged per read query not per row thats kinda crazy
Ptbh it sounded like a fun excuse to do more with cloudflare and that’s all I really paid attention to 
1Honestly if you ignored costs there's probably a dozen different ways to use CF products to do this
1I'll always take more opportunities to build diff stuff on CF
PSame
HThough note WAE can perform sampling
1I found this really interesting, not only to help me understand more generally how RPC works under the hood, but also how I can improve some of my dx and implement useful patterns like OCAN. Definitely can't wait to see where you take Lumenize, unless CapnWeb takes over (which it seems like you aren't convinced on the standard yet)
Hdoes anyone know if the KV backend DOs have a 30s limit, or if they also respect the 5m limit if set? docs are kinda ambiguous
Halso, does anyone know if memory or logging of out-of-memory are improved on the sqlite backend?
1There's basically no reason to still be using the old KV backend
HAsking because we're running into DO issues with memory exceeded (on requests that aren't using 128mb of memory), but it's not worth the migration (deleting all DO objects and remaking under a diff name) for us if the only diff is the storage change
LI've never actually seen this be a problem for me (after panicking about it when I first started using DOs) but more than one instance of the same DO can share the same 128MB. Cloudflare must be smart about sensing that and not loading them that way if they are prone to use more than half the memory but do you think that might be going on?
LYou can sense if that is happening by storing a counter in global context. That global context is shared across instances if they are running in the same 128MB memory.
LIs there a nuanced writeup comparing and contrasting extending RpcTarget vs DurableObject?
LCost-effective external API calls from Durable Objects using Cloudflare Queues
LHere's a diagram showing how it works
JSad DX has to be such that we need to build things like proxy-fetch.
We either use waitUntil, queues or workflows to avoid wall-time specially for inference call scenarios. C'est la vie.
We need an out-of-the-box solution.
We either use waitUntil, queues or workflows to avoid wall-time specially for inference call scenarios. C'est la vie.
We need an out-of-the-box solution.
1What's the delay from sending off the proxy fetch to it being returned? My issue with Queues was always that few seconds delay while the queue is receiving the event
LIt varies wildly, but with this Queues-based variety, you should count on 2-3 seconds p90. As @Jehu wrote, just making the fetch from the DO is often the right choice. It could turn out that the diagram might be the most valuable thing about pushing this out, but maybe someone will find it useful.
We're also working on the docs for a variety that's based upon Durable Objects. Its latency depends upon where in the world the proxy DO is in relation to the DO that makes the fetch. I don't have numbers, but my guess is that same co-lo, you'd be talking no more than 20ms latency, on top of the fetch itself of course. You can stand up an instance of it in each region, which will cost ~$4/month each from Cloudflare but we're hoping to also offer it as a service for about the same, except we take care of scaling and world-wide co-lo. Sad part is, we're essentially re-inventing Queues.
That version also does streams and SSE but we are struggling to live test demo those features and may only release that as a service.
We're also working on the docs for a variety that's based upon Durable Objects. Its latency depends upon where in the world the proxy DO is in relation to the DO that makes the fetch. I don't have numbers, but my guess is that same co-lo, you'd be talking no more than 20ms latency, on top of the fetch itself of course. You can stand up an instance of it in each region, which will cost ~$4/month each from Cloudflare but we're hoping to also offer it as a service for about the same, except we take care of scaling and world-wide co-lo. Sad part is, we're essentially re-inventing Queues.
That version also does streams and SSE but we are struggling to live test demo those features and may only release that as a service.
1How do I tag mods or is there a ? command for spam like this
LThere is a report post feature in the Discord
...What's the error you'll get if you exceed the pending outgoing fetch limit? I know the current in flight limit is 6, but I've tried getting 200 in flight at the same time and I haven't exceeded that limit or gotten an error. This is in vitest-pool-workers so maybe I need to experiment in prod?
1Definitely wanna test in prod first
LYou don't get an error when you have more than 6, they just get queued and once one completes another one runs. The error is when you are more than 1000 by default I think.
LThanks. What are the details of the error so I can catch it specifically? Or should I just send 2000 and see?
C2 [ sse / durable object ] questions please. 1) There is a lovely blog about hibernating ws's, is this something we should also do for sse's? 2) How does pricing for sse's work please?
ty!!!
ty!!!
HHibernation is only available for WebSockets at the moment
CThanks for the info! Do we get charged for like amount of time writers exist in do's, here's the simple prototype that I'd like to build up, unless it'll we are charged for each moment the do exists!
worker:
html:
worker:
html:
Cdurable object: