rpc has limit of i think 1mb arguments/response over the wire
rpc has limit of i think 1mb arguments/response over the wire
5 Duration billing charges for the 128 MB of memory your Durable Object is allocated, regardless of actual usage. If your account creates many instances of a single Durable Object class, Durable Objects may run in the same isolate on the same physical machine and share the 128 MB of memory. These Durable Objects are still billed as if they are allocated a full 128 MB of memory.
this.state.getWebSockets()?wrangler dev in each folder? Or should i have all the DO bindings defined on a root wrangler.toml? In my case I have a sveltekit app that I'm also deploying on a worker, and was wondering if I should be defining all my DO bindings on my sveltekit wrangler.toml ---inspect-brk you'll see exactly where time is being spent. I think once you've optimized on your side the only thing you can do is architect your DOs and Workers in a way that they're closer to your users which is another topic + what we're dealing with now (moveable DOs when pls)namespaceId and objectId were added as dimensions to the durableObjectsStorageGroups in the graphql API, so we could calculate used storage per DO instanceINSERT operation against the storage returns 2 rowsWritten , although I only inserted one row, is this normal behavior or am I missing something?rowid?WITHOUT ROWID the sequence of written data is not ordered as before