You don't have to keep that much state in memory at all, actually. I'm not sure why you think that you do. Most of the state resolution (eg. the auth chain) in

You don't have to keep that much state in memory at all, actually. I'm not sure why you think that you do. Most of the state resolution (eg. the auth chain) involves calculations of which you can cache the result without needing to care about the inputs beyond that - at least, unless you need to recalculate them once later if delayed events come in. Ultimately, the performance problems that Synapse has are problems with Synapse's implementation choices (especially around the database schema), not with the protocol nor with the state resolution algorithm.