Only invalidate membership caches based on the cache stream
Before we completely invalidated get_users_in_room whenever we updated any current_state_events table. This was way too aggressive.
Showing
- synapse/replication/resource.py 0 additions, 3 deletionssynapse/replication/resource.py
- synapse/replication/slave/storage/events.py 5 additions, 16 deletionssynapse/replication/slave/storage/events.py
- synapse/storage/events.py 0 additions, 20 deletionssynapse/storage/events.py
- synapse/storage/roommember.py 0 additions, 2 deletionssynapse/storage/roommember.py
Loading
Please register or sign in to comment