What limits have you increased, and to what new limit (if you're allowed to talk about specifics)? I

What limits have you increased, and to what new limit (if you're allowed to talk about specifics)? I haven't needed to yet, but want to make sure I'll be covered in the future

Hhunt is there a reason we have to do this instead of using the DO stub as if it were ...

1984 Ford LaserOP•2/18/25, 10:59 PM

That doc note is mostly just to define the basic way that a stub is accessed after it is initialised. The reasoning for needing RpcTarget is to do with DO stubs on their own not being serializable, but RpcTarget is

11984 Ford Laser What limits have you increased, and to what new limit (if you're allowed to talk...

hunt•2/18/25, 11:03 PM

worker size & num of workers are the ones that are top of mind (I think we got a 5x increase?)

Hhunt my implementation of this in case anyone is curious

hunt•2/19/25, 3:06 AM

a continuation on my fact finding mission:

Returning an RpcTarget from a WorkerEntrypoint shows `never` for method return types

(this isn't really a durable objects problem and more of an "rpc types" problem so I'm taking it there)

Frank•2/20/25, 1:44 AM

we needed to delete a DO from our stack today. removed binding from wrangler.ymlwrangler.yml and added a deleted_classesdeleted_classes migration, but it still complained about worker binding not removed.
ended up having to remove it from CF dashboard, then redeploy from wrangler

Frank•2/20/25, 1:44 AM

is this expected

TTyveris I'm trying to create a worker that is connected to with websockets, but then the...

boop•2/20/25, 5:52 PM

Wrap your code in backticks

```

```

TTyveris I'm trying to create a worker that is connected to with websockets, but then the...

hunt•2/20/25, 6:38 PM

the socket itself lives in the memory of the request context (same with the userId). Any state in your fetch handler wont get garbage collected until the request context is finished (or when the connection is closed)

TTyveris I'm trying to create a worker that is connected to with websockets, but then the...

hunt•2/20/25, 6:52 PM

can I ask what your use case is where you use websockets instead of something basic like an http router? do you just need to thread events back to the client as things are happening?

tornado•2/20/25, 8:20 PM

Is there any reason to delete durable objects? If I'm understanding the limits page right, I can have unlimited objects and objects that aren't being used aren't charged, why would I delete any object?

TTyveris Yeah, backend for a multiplayer game, expecting notifications and shared DOs lik...

1984 Ford LaserOP•2/20/25, 10:03 PM

You'll wanna make sure you use the Hibernation API by invoking this.state.acceptWebSocket(socket)this.state.acceptWebSocket(socket) instead of socket.accept()socket.accept() to avoid massive charges

Jacob Marshall•2/21/25, 7:05 AM

Is there any advice from the Cloudflare team around how to import a SQL dump file into a Durable Object (with SQLite backend, obviously) when the dump is larger than the memory limit for a Durable Object (128 MB)? I can't think of how this could be achieved (within a single transaction, that is). To be clear - I don't currently have this problem... but I'm trying to figure out if it's going to be one in the future. Thanks!

JJacob Marshall Is there any advice from the Cloudflare team around how to import a SQL dump fil...

lambrospetrou•2/21/25, 7:34 AM

You can use streams to process the request without having the whole file in memory. However, doing hundreds of MBs or GBs will probably need you to split it in smaller chunks otherwise you will hit cpu/time limits.
Example of streaming a file in DO: https://github.com/lambrospetrou/tiddlyflare/blob/main/src/durable-objects.ts#L281

Llambrospetrou You can use streams to process the request without having the whole file in memo...

Jacob Marshall•2/21/25, 8:20 AM

Cheers. Yeah, I figured I'd have to do it async (with streams). Hopefully someday it'll be possible without that though

JJacob Marshall Cheers. Yeah, I figured I'd have to do it async (with streams). Hopefully someda...

lambrospetrou•2/21/25, 8:21 AM

I doubt that. You will always have less memory than what people need for bulk imports. Streaming is the way to go.

Llambrospetrou I doubt that. You will always have less memory than what people need for bulk im...

Jacob Marshall•2/21/25, 8:22 AM

A man can dream can't he haha

Matt•2/21/25, 6:32 PM

So as I understand it, if you use storage.put()storage.put() multiple times without awaiting, it will group all the writes into a single round trip. If you

put

put

to the same key multiple times without awaiting, will it write to that key multiple times or will it only write the last one?

TTyveris So with durable objects, if you plan to make api calls, it seems like its best t...

hunt•2/22/25, 3:19 AM

An approach you could consider is using a hybrid of rest and websockets. Instead of trying to create one layer of abstraction, you let rest do the thing it's good at which is handling transactional requests, and let websockets handle what it's good at which is streaming data.

Your clients would subscribe to an "event stream" DO with a user id, and when you're handling transactional requests and need to push an event to any client, you call the DO with the event and user id which then pushes that off to the client

atgctg•2/22/25, 11:40 AM

Is there a better way to make a value available in a DO's constructor? This is the only way I found:

app.get('/avatars', async c => {
  const user = c.get('user')
  c.env.uid = user.uid // is this a bad practice?
  const userObjectId = c.env.USER_OBJECT.idFromName(user.uid)
  const userObject = c.env.USER_OBJECT.get(userObjectId)
  const avatars = await userObject.getAvatars()
  return c.json(avatars)
})

app.get('/avatars', async c => {
  const user = c.get('user')
  c.env.uid = user.uid // is this a bad practice?
  const userObjectId = c.env.USER_OBJECT.idFromName(user.uid)
  const userObject = c.env.USER_OBJECT.get(userObjectId)
  const avatars = await userObject.getAvatars()
  return c.json(avatars)
})

Aatgctg Is there a better way to make a value available in a DO's constructor? This is t...

lambrospetrou•2/22/25, 1:06 PM

I doubt this works. Did you test it? You are modifying a local variable here, not the actual env injected into your worker/DO if it happens to be created in a different machine or even a different isolate/process.
If you want data in your DO that are not in the envenv, you need to pass them in your RPC call to the DO.

Llambrospetrou I doubt this works. Did you test it? You are modifying a local variable here, no...

atgctg•2/22/25, 1:09 PM

The variable shows up on env, but only tested locally.
Just would have been nice to be able to initialize it in the constructorconstructor, I might make an

init

init

method so I don't have to pass it on every call

Aatgctg The variable shows up on env, but only tested locally. Just would have been nice...

lambrospetrou•2/22/25, 1:11 PM

See https://developers.cloudflare.com/reference-architecture/diagrams/storage/durable-object-control-data-plane-pattern/

Cloudflare Docs

Control and data plane architectural pattern for Durable Objects · ...

Durable Objects are built on-top of Cloudflare Workers spanning several locations across our global infrastructure network.
Each Durable Object instance has its own durable storage persisted across requests, in-memory state, single-threaded execution, and can be placed in a specific region.

Llambrospetrou See https://developers.cloudflare.com/reference-architecture/diagrams/storage/du...

atgctg•2/22/25, 1:23 PM

That's a great resource, thanks.
So based on that, I think I should call init(uid)init(uid) the first time the user object is created, save the user's id to storage, and this way it will be available in storage whenever I'm calling that DO again, right? Just need to set it in the constructorconstructor like this:

ctx.blockConcurrencyWhile(async () => {
  this.uid = await ctx.storage.get('uid')
})

ctx.blockConcurrencyWhile(async () => {
  this.uid = await ctx.storage.get('uid')
})

Aatgctg That's a great resource, thanks. So based on that, I think I should call `init(u...

James•2/22/25, 4:11 PM

I’m conservative on rpc calls and to avoid unnecessary round trips, I just pass a metadata obj to all my rpc calls as an optional arg which defaults some helpful initialization stuff to the DO

1984 Ford LaserOP•2/23/25, 7:32 AM

Anyone know if partysub has a limit on the number of topics that can be specified?

TTyveris Specific questions: 1. Is it ok to pull the websocket property off the internal ...

geg•2/23/25, 5:21 PM

This is how it's done, you're on the right track

TTyveris It seems like it is possible to create a WebSocket connection from a worker to a...

Franco Romano Losada•2/23/25, 6:39 PM

Have you tried PartyServer (https://github.com/threepointone/partyserver/tree/main). You avoid a lot of boilerplate and get some good things too. I was doing it like do but from Hono but this library is nice, and provides a nice client too

chronark•2/24/25, 9:25 AM

anyone else getting a ton of errors right now from durable objects?

- Internal error in Durable Object storage write caused object to be reset.Internal error in Durable Object storage write caused object to be reset.
- Network connection lost.Network connection lost.

1984 Ford LaserOP•2/24/25, 10:43 AM

Why would this code cause 2 DO read operations when a websocket client connects then immediately disconnects?

11984 Ford Laser Why would this code cause 2 DO read operations when a websocket client connects ...

Isaac McFadyen•2/24/25, 11:04 AM

You're checking path but not method I expect

Isaac McFadyen•2/24/25, 11:04 AM

I assume that you're trying to connect a WebSocket for the initial OPTIONS preflight and that's causing the extra request

Isaac McFadyen•2/24/25, 11:04 AM

Assuming WS sends preflight

IIsaac McFadyen You're checking path but not method I expect

1984 Ford LaserOP•2/24/25, 11:04 AM

The path check is in the Worker not the DO

11984 Ford Laser The path check is in the Worker not the DO

Isaac McFadyen•2/24/25, 11:05 AM

Yeah but if it's an OPTIONS preflight the DO will still be spawned because of the get() and fetch()

Isaac McFadyen•2/24/25, 11:05 AM

From the Worker

1984 Ford LaserOP•2/24/25, 11:06 AM

Im connecting using Postman, haven't noticed any OPTIONS requests in the real time logs

Isaac McFadyen•2/24/25, 11:07 AM

Hmmm OK maybe not that then

1984 Ford LaserOP•2/24/25, 11:07 AM

I also respond to options preflight earlier in the worker prior to pulling a stub

1984 Ford LaserOP•2/24/25, 11:10 AM

Also shouldn't a DO read operation only happen when accessing storage, not pulling the stub itself?

11984 Ford Laser Also shouldn't a DO read operation only happen when accessing storage, not pulli...

lambrospetrou•2/24/25, 12:58 PM

Yes, just getting the stub and going into the DO doesn't cause any storage operation.
From the snippet you shared, I am not sure if

acceptWebSocket()

acceptWebSocket()

does any storage operation, like reading something and updating it with the new socket, since it needs to somehow persist that.

Llambrospetrou Yes, just getting the stub and going into the DO doesn't cause any storage opera...

Milan•2/24/25, 1:44 PM

acceptWebSocket()

acceptWebSocket()

doesn't do any storage operations (see hibernation-manager.c++).

GitHub

workerd/src/workerd/io/hibernation-manager.c++ at 2f7d61d69f5066836...

The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd

cloudkite•2/24/25, 7:35 PM

Is there any documentation/guidance around what happens when you update your DO script. Found https://community.cloudflare.com/t/durable-objects-state-during-lifecycle-events/319932/5 does that same restriction apply when using this.ctx.storage.sql?

cloudkite•2/24/25, 7:38 PM

Would be great if ongoing requests are given chance to complete, rather than throwing error when storage API is accessed, as this will cause breakages in our usecase.

What limits have you increased, and to what new limit (if you're allowed to talk about specifics)? I

Similar Threads