I had a number of users all editing large documents (>50MB) when disaster struck. The standard
y-webserver runs in
nodejs and keeps open documents in memory to serve to clients when they connect.
nodejs, however, comes with 512MB maximum heap size out of the box. In my case, it ran out of heap and crashed. This was particularly problematic because before or while it was crashing,
y-webserver sent empty documents back to the connected clients, effectively deleting them.
The moral is that you should watch out that
node is started with enough memory. This can be done with a larger setting than the 512 MB default for
/usr/bin/node --max-old-space-size=4096 /path_to/node_modules/.bin/y-websocket-server