Milan
CDCloudflare Developers
•Created by ᴀkqj on 2/7/2025 in #durable-objects
Hey team 👋 , I am having issues with
In other words, you send a request that hogs CPU for a while, and a bunch of requests queue up waiting to be delivered, but because DOs are single threaded, only 1 request can be processed at a time. Eventually some requests wait for too long and we say we failed to deliver the request.
2 replies
CDCloudflare Developers
•Created by ᴀkqj on 2/7/2025 in #durable-objects
Hey team 👋 , I am having issues with
IIRC I believe this means your DO is taking too long to process requests. The 1000 RPS means 1000 requests where you immediately
return new Response("OK") (fwiw the last I checked we can handle more, but it's hard to define a limit when it's so dependent on your application code).2 replies
CDCloudflare Developers
•Created by 1984 Ford Laser on 1/16/2025 in #durable-objects
Okay this is a dumb one, I think I fixed
It's always a bit tricky to sufficiently document these things, since this is more of a "how websockets work" kinda thing, less of a "how to use websockets on our platform" kinda thing.
8 replies
CDCloudflare Developers
•Created by 1984 Ford Laser on 1/16/2025 in #durable-objects
Okay this is a dumb one, I think I fixed
I think our examples (1, 2) show this (if we receive a close we reply with a close back), you'd want to do something similar on the client.
8 replies
CDCloudflare Developers
•Created by 1984 Ford Laser on 1/16/2025 in #durable-objects
Okay this is a dumb one, I think I fixed
Sorry, didn't get a notification for this. Just a heads up but you might find this useful https://datatracker.ietf.org/doc/html/rfc6455#section-5.5.1
If an endpoint receives a Close frame and did not previously send a Close frame, the endpoint MUST send a Close frame in response. (When sending a Close frame in response, the endpoint typically echos the status code it received.) It SHOULD do so as soon as practical. An endpoint MAY delay sending a Close frame until its current message is sent (for instance, if the majority of a fragmented message is already sent, an endpoint MAY send the remaining fragments before sending a Close frame).
8 replies
CDCloudflare Developers
•Created by egg on 2/3/2025 in #durable-objects
@quan @1984 Ford Laser It was definitely
I didn't really know about this myself til someone else on discord started asking about disconnects. This isn't enforced by Workers/DOs, it's enforced by some place deeper in the Cloudflare stack so we weren't aware of it 😅 . Will look into getting it added to the docs somewhere.
11 replies
CDCloudflare Developers
•Created by egg on 2/3/2025 in #durable-objects
@quan @1984 Ford Laser It was definitely
@egg this would be my default guess https://developers.cloudflare.com/fundamentals/reference/tcp-connections/#:~:text=If%20either%20a%20user%20or,alive%20probes%20every%2075%20seconds.
11 replies
CDCloudflare Developers
•Created by 1984 Ford Laser on 1/16/2025 in #durable-objects
Okay this is a dumb one, I think I fixed
Sounds good, I'm actually gonna be out for a bit too, can circle back early Feb 🙂
8 replies
CDCloudflare Developers
•Created by 1984 Ford Laser on 1/16/2025 in #durable-objects
Okay this is a dumb one, I think I fixed
This still seems weird? Maybe I don't properly understand the situation, but if your DO wasn't receiving messages the DO should still hibernate. Unless you just mean your DO was trying to do work but wasn't able to because the WS client had gone away
8 replies