-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix frequent "disconnects" #152
Comments
➤ Rafal Dittwald commented: I suspect it has something to do with a long running transaction; |
Seeing this still, in conjunction with extremely high CPU usage, right after a new user joined...there's also a group that seems to have some sort of corrupted state (see #194) which is maybe a causal factor. |
Observation: CPU spikes on the server right after a message is sent but if the thread the message is in doesn't have any tags, only @-mentioned users, it seems okay. Issue calculating message visibility based on tags? |
Related #152 braid.core.server.sync-helpers/notify-users was repeatedly looking up users-for-user and tags-for-user (via message-format/parse-tags-and-mentions), which was a holdover from back when threads could be in multiple groups. Also, it was blocking. Reduced the repeated looping and put it in a future..
No description provided.
The text was updated successfully, but these errors were encountered: