Interesting thanks for this. How big was your worker and what performance gains did you observe? @Be
Interesting thanks for this. How big was your worker and what performance gains did you observe? @Beefp
---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
never. Anyone had this before?
---inspect-brknamespaceIdobjectIddurableObjectsStorageGroupsrowsWrittenrowidWITHOUT ROWID