Hi @braden,
The main advantage of using Yjs is that you can scale indefinitely using a simple pubsub server to propagate document updates.
The memory usage of representing a conference paper (see this post) is about ~2MB (260k edits). Although there currently seems to be some bug in y-websocket which blows up memory.
I plan to rework y-websocket server not to load the document to memory at all. I explained my plans in the post you mentioned. Eventually, I’d like to be able to handle 100k connections on a single websocket server.