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

presence processing pins the cpu for hours after joining a large room #5248

Closed
richvdh opened this issue May 24, 2019 · 3 comments
Closed

presence processing pins the cpu for hours after joining a large room #5248

richvdh opened this issue May 24, 2019 · 3 comments
Labels
A-Performance Performance, both client-facing and admin-facing

Comments

@richvdh
Copy link
Member

richvdh commented May 24, 2019

for literally hours after joining a large room like HQ, we get stuck in a loop that looks like this:

2019-05-24 12:46:37,301 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@freenode_aOssed-:matrix.org', $1534927445346266LDGwg:matrix.org
2019-05-24 12:46:37,301 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@ziccardi:matrix.org', $1542290119314550ekjkP:matrix.org
2019-05-24 12:46:37,301 - synapse.state - 178 - DEBUG - presence.notify_new_event-91- calling resolve_state_groups from get_current_users_in_room
2019-05-24 12:46:37,301 - synapse.state - 358 - DEBUG - presence.notify_new_event-91- resolve_state_groups event_ids ['$155869549715439HHnCI:matrix.org']
2019-05-24 12:46:37,315 - synapse.federation.sender.per_destination_queue - 169 - DEBUG - presence.notify_new_event-91- TX [matrix.org] Transaction already in progress
2019-05-24 12:46:37,315 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@debirs:matrix.org', $15535182641013390zENdq:matrix.org
2019-05-24 12:46:37,315 - synapse.state - 178 - DEBUG - presence.notify_new_event-91- calling resolve_state_groups from get_current_users_in_room
2019-05-24 12:46:37,316 - synapse.state - 358 - DEBUG - presence.notify_new_event-91- resolve_state_groups event_ids ['$155869549715439HHnCI:matrix.org']
2019-05-24 12:46:37,330 - synapse.federation.sender.per_destination_queue - 169 - DEBUG - presence.notify_new_event-91- TX [matrix.org] Transaction already in progress
2019-05-24 12:46:37,330 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@root:matrix.silverlane.dotorg.org', $15461114867NGgsb:matrix.silverlane.dotorg.org
2019-05-24 12:46:37,330 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@freenode_rubidious:matrix.org', $15308846451400755JLpKP:matrix.org
2019-05-24 12:46:37,330 - synapse.handlers.presence - 826 - DEBUG - presence.notify_new_event-91- Handling: 'm.room.member' '@pecan:atlantisnet.bg', $153494369824evggm:atlantisnet.bg

It makes the server unusable after joining a large room.

@richvdh
Copy link
Member Author

richvdh commented May 24, 2019

this contributes to the general joining-rooms-is-awful of element-hq/element-web#1211 / https://github.com/vector-im/riot-web/issues/2076

@richvdh richvdh added the A-Performance Performance, both client-facing and admin-facing label May 24, 2019
@richvdh
Copy link
Member Author

richvdh commented May 24, 2019

oh, I think this might be a dup of element-hq/element-web#5157, since I'm seeing that error repeatedly too. I'd be inclined to fix that and see if this goes away.

@richvdh
Copy link
Member Author

richvdh commented Jan 6, 2020

well, I think it's better than it used to be. there's still lots of presence; cf element-hq/element-web#3120.

@richvdh richvdh closed this as completed Jan 6, 2020
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
Projects
None yet
Development

No branches or pull requests

1 participant