Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Logging in can cause CPU spike due to device lists #4934

Closed
erikjohnston opened this issue Mar 26, 2019 · 1 comment
Closed

Logging in can cause CPU spike due to device lists #4934

erikjohnston opened this issue Mar 26, 2019 · 1 comment
Assignees
Labels
A-Performance Performance, both client-facing and admin-facing z-bug (Deprecated Label) z-outbound-federation-meltdown (Deprecated Label) Synapse melting down by trying to talk to too many servers

Comments

@erikjohnston
Copy link
Member

@babolivier has this.

Basically, sending the log in request caused synapse to start sending tonnes of outbound device list updates to all the servers he shared a room with. This seems to have caused synapse to use 100% CPU and slowed down the processing of the /login request sufficiently for the client to time out, resulting in him not being able to log in.

@neilisfragile neilisfragile added z-bug (Deprecated Label) A-Performance Performance, both client-facing and admin-facing labels Mar 29, 2019
@hawkowl hawkowl self-assigned this Jul 11, 2019
@hawkowl hawkowl added the z-outbound-federation-meltdown (Deprecated Label) Synapse melting down by trying to talk to too many servers label Jul 11, 2019
@ara4n
Copy link
Member

ara4n commented Mar 19, 2022

dup #7721.

@ara4n ara4n closed this as completed Mar 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Performance Performance, both client-facing and admin-facing z-bug (Deprecated Label) z-outbound-federation-meltdown (Deprecated Label) Synapse melting down by trying to talk to too many servers
Projects
None yet
Development

No branches or pull requests

4 participants