Storage Ops when connecting to DO Hibernatable Websockets

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

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

So I was able to reproduce this with a fresh Worker, absolute minimum implementation of Hibernatable Websockets, and I am still seeing 2 read ops, 0.1-0.7 GB-sec compute (which feels very high to connect to a DO then immediately disconnect), and an initial request wall time of up to 700ms. This is consistent on both KV and SQL backend DOs. I have written a basic chat app in the past using DO WS and all usage for the initial connection was always very reasonable

Storage Ops when connecting to DO Hibernatable Websockets

Similar Threads

Similar Threads

Similar Threads