From 2207b525d44d121e9be5e5ee113de19b51caffea Mon Sep 17 00:00:00 2001 From: Giom Foret Date: Wed, 27 Sep 2023 18:59:03 +0200 Subject: [PATCH] Add a reference to MSC3013 Encrypted push --- .../4028-push-all-encrypted-events-except-for-muted-rooms.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md b/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md index defa29aca03..b5ae3970f70 100644 --- a/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md +++ b/proposals/4028-push-all-encrypted-events-except-for-muted-rooms.md @@ -108,6 +108,8 @@ The clients with push services will request more frequently the server to retrie This may be a potential performance issue if each client fetches separately each pushed event. But this should not be the case, because the clients have to run a sync if they want to be able to receive potential new encryption keys through to_devices. So they will retrieve more than one event at the time. +BTW [MSC3013: Encrypted Push](https://github.com/matrix-org/matrix-spec-proposals/pull/3013) could potentially mitigate this. + #### Push sending Push is a huge bottleneck on the sending side. So calculating what to push and the unread counts (its the same process) is a big performance bottleneck currently when sending in large rooms. A bunch of optimisation has taken place to make that better, but its still quite expensive. We should plan an effort to limit potential issue server side here.