You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The room state cache gets saved to disk on almost all Room::change events.
That state can be multiple MB and is freshly written on every new message.
Is this necessary or is it possible to limit this?
The text was updated successfully, but these errors were encountered:
This was made as low-maintenance way to store the room state back before we had to have a database. I think saving the most recent state is valuable to make sure it doesn't get lost in case of crashes but if we save it to the database instead of a CBOR file we could at least save it in a more fine-grained manner, into a file that is already open anyway.
The room state cache gets saved to disk on almost all Room::change events.
That state can be multiple MB and is freshly written on every new message.
Is this necessary or is it possible to limit this?
The text was updated successfully, but these errors were encountered: