Ah but I assumed the DO was loaded into memory and thus the 128MB was the “size” of the DO
Ah but I assumed the DO was loaded into memory and thus the 128MB was the “size” of the DO
LDurable Objects are code like Workers, and they have durable storage you can use up to 10GB. They don't load all that storage in memory. Your DO has 128MB to use for its normal code operations, and tha'ts what you are charged for duration. The durable storage itself is charged separately.
Read https://developers.cloudflare.com/durable-objects/platform/pricing/ if you haven't.
Read https://developers.cloudflare.com/durable-objects/platform/pricing/ if you haven't.
TAh thanks for the clarification
Banyone knows how long it takes to get into the realtimeSDK beta? I applied on the 17th of april and did not get in yet
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.FHey everyone!
I have a C++ application, that creates its own sqlite database for its internals. I want to use it in a Cloudflare Durable Object. I recompiled to Webassembly, created Emscripten bindings, so now I can trigger the creation of the aforementioned database from JS, in a Durable Object class.
Question:
https://developers.cloudflare.com/durable-objects/api/storage-api/#sql-api
Thanks
I have a C++ application, that creates its own sqlite database for its internals. I want to use it in a Cloudflare Durable Object. I recompiled to Webassembly, created Emscripten bindings, so now I can trigger the creation of the aforementioned database from JS, in a Durable Object class.
Question:
- is this setup taking advantage of the Durable Object setup ?
- or in other words, do I have to feed my query strings to
this.sql.exec(...) - or is the db created by my C++/WASM code is just as fast?
https://developers.cloudflare.com/durable-objects/api/storage-api/#sql-api
Thanks
Cloudflare Docs
The Durable Object Storage API allows Durable Objects to access transactional and strongly consistent storage. A Durable Object's attached storage is private to its unique instance and cannot be accessed by other objects.
LYour WASM database will definitely be slower. And unless you use the DO storage I don't see how your changes will be durably persisted if you only do them inside WASM.
Vwhen adding
limitoffset
LDepends on your queries, we have folks doing hundreds of thousands of rows read per second, and we have seen a few low millions too. It depends how many of these queries you have in parallel since your DO will be blocked for that amount of time per request.
A few low/single-digit thousands should be a good ballpark to start with to still stay within a few milliseconds.
A few low/single-digit thousands should be a good ballpark to start with to still stay within a few milliseconds.
Vyes i was planning on doing that but i thought saying limit/offset would get my point across better
Fi have singleton pubsub in cpp
I use emscripten::val to call js from c++
using QueryCallback = std::function<void(const std::string &)>;
c++ publishes and I in my bindings I subscribe with a function that calls into JS, and passes query string
val jsFunc = val::global("printName");
QueryCallback cb = [&jsFunc](const std::string &query) { jsFunc(query); };
pubsub_singleton.addListener(cb);
I use emscripten::val to call js from c++
using QueryCallback = std::function<void(const std::string &)>;
c++ publishes and I in my bindings I subscribe with a function that calls into JS, and passes query string
val jsFunc = val::global("printName");
QueryCallback cb = [&jsFunc](const std::string &query) { jsFunc(query); };
pubsub_singleton.addListener(cb);
Fi'd be a lot nicer with a C++ API 
AWhy is there no ability to list the DO instances (or at least the number of them) on the web dashboard? I get that it is accessible via the REST API, but it seems like something that should be on the dashboard... (unless I am missing something)
FHas anyone built a sharding library for DOs to grow dynamically once req/s or storage limits are hit? I remember seeing something like that at some point in this chat
Ahow much time after the last user disconnects will a DO spin down?
Ai need to know because we have some long-running async tasks to run
Awondering if we need e.g.
waitUntil()
HIIRC
waitUntilThe request context for a Durable Objects extends at least 60 seconds after the last client disconnects. So waitUntil is not necessary. It remains part of the DurableObjectState interface to remain compatible with Workers Runtime APIs.
LI have that in progress for my own library (
durable-utils
Aoh interesting. that makes me nervous though... i have some DO code that essentially works like a regular HTTP router and i'm using waitUntil for good measure
Awhy even expose that if it's truly a no-op? 
HIt remains part of the DurableObjectState interface to remain compatible with Workers Runtime APIs.
HIIRC because many things built for Workers expect
ExecutionContextYour DO will stay active after the last request up to 1-2 minutes if you have some
If you want to keep it running for longer you can schedule an alarm to run every few seconds doing nothing other than checking if your long running tasks are done and rescheduling itself if not yet. Alarms count as normal requests so they reset the timer for eviction.
setTimeout/setIntervalIf you want to keep it running for longer you can schedule an alarm to run every few seconds doing nothing other than checking if your long running tasks are done and rescheduling itself if not yet. Alarms count as normal requests so they reset the timer for eviction.
Awhat about a pending promise?
SHow do you export a DurableObject in a Next.js app using OpenNext on Workers?
LIf you refer to websocket hibernation, then no, you do not pay for duration once the DO is hibernated.
Note that if you use
Note that if you use
setTimeout/setInterval
Tare there any disturbances with durable objects? One of objects started throwing errors when opening websockets at 18:30 UTC and it still continues. Other instances work fine. All calls to open a websocket end in a error with some internal code, for example:
internal error; reference = keblnpj3s5njtsgrk5tjitk3
JSomehow DO alarms get called everytime i refresh the static page
MHmm, are you maybe setting the alarm to run in the constructor? Alternatively, are you calling the
alarm()Not natively, though you should be able to dump the SQL manually
PI must admit I am still amazed this is not the #1 priority and next feature for DO (I mean native backup/restore procedures through a R2 integration or else).
GGotherwise you could have it write to d1 and use d1s dump feature
AI get DO's that get stuck in an
This has been reported long time ago and marked as resolved but it doesn't look resolved for me: https://github.com/cloudflare/workerd/issues/2993#issuecomment-2801468494
I have tried emptying the
alarmThis has been reported long time ago and marked as resolved but it doesn't look resolved for me: https://github.com/cloudflare/workerd/issues/2993#issuecomment-2801468494
I have tried emptying the
alarm
Smy assumption is still that the outerbase people are cooking something cool in regards of DO storage
SIs this just impossible?
AIs this still an issue that's somehow hidden now? I don't have Smart placement turned on (it's on "default") but I am still getting this
RPC receiver does not implement the method [x]not impossible but not recommended anyway workers-and-pages-discussions
Sbut it would require you to change the built code
SThanks! Makes sense.
FHi
In WSL open devtools does not pop up anything, other commands work fine.
Did anyone run into this?
In WSL open devtools does not pop up anything, other commands work fine.
Did anyone run into this?
GI use Durable Objects in remix and I made it so there is a backend worker handling the Durable Object for each customer (they get a unique instance each), and the remix app uses RPC to interface with the worker
SGdispose the stub?