Post

Being bad at Cloudflare Workers is extremely expensive

what bit you, cpu-bound work eating wall time or subrequest fanout? building a pdf fill/merge api on workers, our surprise was buffer ops burning active-cpu ms fast enough to matter once we hit the paid tier's pricing model.

Durable Object Row Reads. 3 trillion in a week. I was building a labeler and saved off millions of events from the jetstream for debugging. I had a watchdog doing health and status, and I tacked on to it a garbage collector for stale records and it did a full table scan every 30 seconds. It was a

bad design anyways since I hadn't created an index for what I was querying for, but I didn't realize the Workers Paid plan had billable usage. I truly thought it was fixed at $5/mo lmaoo