Dmytro Maretskyi

`Indexer` does parititioning by space key, and each concrete index implementation doesn't know about partitioning

Can potentially result in broken runtime state of the database on the vault

Closed in https://github.com/dxos/dxos/pull/6643/commits/188eb346211bbd231559d4bcdfa053bed5508db1

needs repro

- `open`/`close` status should not be persisted in echo between reloads - `open`/`close` status shoudl not influence other sessions to the same worker -- on the worker we should count...

> problem: its too expensive to have everything open on startup The most performance-intensive thing for an open space is network replication. We might wanna consider toggling that instead of...

https://composer.dev.dxos.org/2c5c10a8d82eab3a52b30522c14e3f3e37ea3ead365cd7c74e8d3830d313cdd5

I think the startup time can be largely reduced by just not querying every space. I'd recommend starting with that first, and then comming back to not openning spaces if...

Can confirm i'm seeing variations of this too: couple times the UI didn't load at all for the new peer.

I've tried reproing in testbench but currently blocked on https://github.com/dxos/dxos/issues/6712