-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Riot stalls when receiving messages #6060
Comments
It's officially reached the point where I can only use Riot if I wish to type messages blind because it can't keep up with what I'm typing or clicking. Here's a profile containing 1.7 minutes of frustration. In it, I check a couple rooms and try to send 2 messages in another room. lots-of-pauses.zip (6mb compressed; 84mb uncompressed) |
It looks like it's churning pretty badly on trying to figure out if badges should be displayed or not. The flame graph shows a few places where it takes several seconds to |
For the most part this has gone away. Conveniently, my homeserver is also not trying to set itself on fire anymore. I have a feeling it's somewhat related. |
... and I've narrowed it down to receiving messages causing an app-wide stall. Easily reproduced on my account by sending 3 or more messages in another client. The faster the messages come in, the longer riot pauses. This correlates with the flame graph where it's trying to reorganize my massive room list. |
This is making riot/develop completely unusable for me. |
Otherwise any function tghat takes longer than the delay to execute will become eligible for execution again immediately after finishing and therefore be able to spin. This should help with element-hq/element-web#6060 (at least in the respect that it makes ratelimitedfunc do its job) even if it's not the reason Riot started getting wedged.
My vote would be to close this following the recent perf work in matrix-org/matrix-react-sdk#1801 and #6313 |
Description
The few places I use riot.im/develop have become particularly bad to use as of today. I've taken a few profiles to hopefully help narrow down what is going on.
riot-slow-jan29-2018.zip (20mb compressed; 260mb uncompressed)
There's 3 profiles in the archive because chrome was getting mad at me. Here's their breakdown:
The only change that I'm aware of was matrix-org/matrix-js-sdk#594 landing. Riot was last "usable" (by a rough standard of not stalling every few seconds) Sunday, Jan 28, 2018.
Version information
The text was updated successfully, but these errors were encountered: