Erik Johnston 29574fd5b3 Reduce federation presence replication traffic ... This is mainly done by moving the calculation of where to send presence updates from the presence handler to the transaction queue, so we only need to send the presence event (and not the destinations) across the replication connection. Before we were duplicating by sending the full state across once per destination.		2017-04-10 16:48:30 +01:00
..
__init__.py	Add a slaved events store class	2016-04-06 14:18:35 +01:00
_base.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
_slaved_id_tracker.py	Fix assertion to stop transaction queue getting wedged	2017-03-15 12:16:55 +00:00
account_data.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
appservice.py	Add appservice worker	2016-08-18 14:59:55 +01:00
deviceinbox.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
devices.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
directory.py	Use cached version of get_aliases_for_room	2016-08-15 11:24:12 +01:00
events.py	Reduce federation presence replication traffic	2017-04-10 16:48:30 +01:00
filtering.py	Add a comment explaining why the filter cache doesn't need exipiring	2016-06-03 11:03:10 +01:00
keys.py	Add more key storage funcs into slave store	2016-07-28 15:41:26 +01:00
presence.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
push_rule.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
pushers.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
receipts.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
registration.py	Add appservice worker	2016-08-18 14:59:55 +01:00
room.py	Change slave storage to use new replication interface	2017-04-03 15:34:19 +01:00
transactions.py	Invalidate retry cache in both directions	2016-11-22 17:45:44 +00:00