diff options
| author | Erik Johnston <erik@matrix.org> | 2020-10-28 12:11:45 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-28 12:11:45 +0000 |
| commit | a6ea1a957e8e38ca3f98d4da32ee49a40fcb4807 (patch) | |
| tree | 43068698506ed93e735b48b785e58fc1d1b464b9 /.coveragerc | |
| parent | Tell Black to format code for Python 3.5 (#8664) (diff) | |
| download | synapse-a6ea1a957e8e38ca3f98d4da32ee49a40fcb4807.tar.xz | |
Don't pull event from DB when handling replication traffic. (#8669)
I was trying to make it so that we didn't have to start a background task when handling RDATA, but that is a bigger job (due to all the code in `generic_worker`). However I still think not pulling the event from the DB may help reduce some DB usage due to replication, even if most workers will simply go and pull that event from the DB later anyway. Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
Diffstat (limited to '.coveragerc')
0 files changed, 0 insertions, 0 deletions