HFor DOs to be deployed in a colo, there needs to be a certain number of datacenters within that colo, for redundancy. If a colo doesn't have enough DCs, it can't run DOs(or at least not without a modicum of disaster recovery)
Sinteresting considering oceania barely has any while south africa has a lot? unless i misunderstood this https://where.durableobjects.live/colo
Where Durable Objects Live
Tracking where Durable Objects are created, wherever you are in the world.
HNot sure I understand what you mean? South Africa(the country) has 3 colos, while the general Oceania area has 11 colos, at least from a visual count
Ssorry meant south america
isnt every circle a datacenter?
“For DOs to be deployed in a colo, there needs to be a certain number of datacenters within that colo”
all i see is that australia has like 7 with 3 of them supporting DOs
while brazil has like 15+ and no DO ones
isnt every circle a datacenter?
“For DOs to be deployed in a colo, there needs to be a certain number of datacenters within that colo”
all i see is that australia has like 7 with 3 of them supporting DOs
while brazil has like 15+ and no DO ones
Sim probably just confused here
Sor is a circle a colo and we dont know about the dcs?
HBasically, a Colo is 1-or-more datacenters within the area of a city. So for example, GRU might be a single datacenter, or it might be 20.
Where Durable Objects Live
Tracking where Durable Objects are created, wherever you are in the world.
HAnd if I remember correctly, the resiliency requirement for DOs is n-datacenters within that colo
Sahh i see i see makes sense thanks
HI always get them mixed up tbh
THi all durableObject experts,
i have a download process that downloads multiple parts from R2, i was wondering if its best practice to use durableObject for download session, every time user download a multipart file, i want to keep track on each part he downloads and if he finish downloading all the parts i want to enqueue an event to a queue.
my other option is to use one durable object for R2 file, and use JWT for session token, so multiple downloads per file are going to be tracking JWT token, part number.
what do you think will be best and why?
i have a download process that downloads multiple parts from R2, i was wondering if its best practice to use durableObject for download session, every time user download a multipart file, i want to keep track on each part he downloads and if he finish downloading all the parts i want to enqueue an event to a queue.
my other option is to use one durable object for R2 file, and use JWT for session token, so multiple downloads per file are going to be tracking JWT token, part number.
what do you think will be best and why?
AWhy is there a cpu_ms limit? If there are several requests in a row, does that increase the cpu limit? Is it possible to deactivate it?
WQuestion about deleting a DO instance which has me confused... even after calling
deleteAlarm() and deleteAll() the Cloudflare API says it still exists via the endpoint /workers/durable_objects/namespaces/<id>/objects... Any insights would be appreciated.
PI’m still facing this issue. My current workaround is storing a reference for the DO so i can run another cleanup later (which eventually helps clean everything up)
I’ve noticed some of them eventually persist after first delete (no additional cleanup) if i don’t touch the DO after a few hrs
I’ve noticed some of them eventually persist after first delete (no additional cleanup) if i don’t touch the DO after a few hrs
HI know that on the backend, once a DO is created, it isn't ever garbage collected. As in, if I create a stub to the same DO ID, it will spawn in the same place, even days/weeks later, even if it doesn't have any storage attached. I'm not sure if that applies to the API too
PIs there a known bug where deleteAll() just doesn't persist unless ran multiple times? I received no follow-up for this durable-objects
HNot quite sure on that end? IIRC
deleteAll() might time out if you need to delete a large amount of objects, but if it fully completes, everything should be deletedPthe promise doesnt fail or reject. it goes through successfully every time
HI would note though, I'm not on the DO team, so above is personal knowledge/experience
BDocs say this only applies to KV-backed DOs
BPI'm using the SQLite storage backend with hardly anything stored. weird deleteAll() behavior
W^^ I'm doing this too. The only thing I can think of is that there's a stub/reference to the particular DO instance in a worker which is preventing garbage collection. The docs describe how to create disposable DO's using alarms, but in practice it behaves quite different.
ADoes anyone know how to make sense of this invoice item? I know this is not the channel for this but the support has been unhelpful for the last 7 months.
ANow, i'm in point of thinking in using more DO but really afraid of breaking the bank...
AFor me, the item above should not have be charged because it is included into the 400,00 GB*S... but instead they have charged me $12.5 for the last 7 months
Mto me this reads as you using 635,516 GB*S, and charges to be in blocks of 1,000,000
Bdid u guys do anything to DO? something that used to work for a year just broke
MNot that I know of? WDYM?
Gyea thats the invoice value not the included usage
Geven if you use 400,001 you would be billed $12.50 because you are billed for the next block of usage
G
UFun to see that cloudflare is still charging in block increments vs per unit :YEP:
MI'd like a sanity check - I introduced a DO in a worker to test some things, but would like to rollback to the code before it was introduced. I can't do so, the error is:
Is it impossible to rollback, or did I miss something? I'm happy to unceremoniously kill all the DOs based on my test code
Is it impossible to rollback, or did I miss something? I'm happy to unceremoniously kill all the DOs based on my test code
MI've bodged around it for now - I checked out the old version I wanted to deploy, modified its wrangler.toml to add a
It feels hacky and I'm wondering if that's the correct way to rollback after you add a DO to a worker.
deleted_classes migration in v0.0.2 and deployed.It feels hacky and I'm wondering if that's the correct way to rollback after you add a DO to a worker.
KAre there any performance issues with spinning up ~100K different DO's / sec? We saw an issue with Workflows where we were getting throttled when kicking off thousands of workflows at once, so wondering if that was also true of DO's.
Scheck the Workflows Limits
HAre they geographically spread out? At that usage, it might be a good idea to contact Support/your CSM if you have one, just to scope out what is possible
TAre there any plans to add "management capabilities" for durable object instances? For example listing instances or removing storage to destroy etc? I don't want to include such temporary/one time logic in my production app, and that pretty much leaves as the only option to build a second "management app" to execute these lifecycle actions (unless I am missing something)?
VHi 
I often get this error, but can't discern a pattern:
Do you have any pointers on what this might be from? Thanks!
I often get this error, but can't discern a pattern: Error: Internal error while starting up Durable Object storage caused object to be reset.Do you have any pointers on what this might be from? Thanks!
Phas anyone attempted to use the new vite plugin support for durable objects? we use remix (< react router 7, will upgrade eventually) across various workers but we've been using mustache templates within our DOs and want to improve DX by switching them to render react components into html (we currently store cached HTML from mustache compilation into the DO sql tables).
KProbably mostly in NA, but it wouldn’t be random. I’m trying to process data from event webhooks, so the same webhook would probably be in the same place.
Kfiled a ticket with support. i'm on the enterprise plan, but should i have a CSM? haha, i didn't know that was an option
HEnterprise Accounts usually have a CSM, but not sure if that is actually a sure thing or not
JIs there a fast way to duplicate the whole sql database on a durable object to a new one?
SNo
AJust to make sure I'm not missing something, is it fair to say that key-value backed Durable Objects are not available on the free plan, and only SQLite-backed ones are? (based on https://developers.cloudflare.com/durable-objects/platform/pricing/#key-value-storage-backend and it not listing any limits for the free tier)