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
Displaying messages is fairly slow #1014
Comments
Right, so there's two issues here that come into play.
The second one is an optimization that I've had on my mind for at least a couple years. I just need to block, say, an entire weekend to fix it, and I've found myself not really willing to do that lately. If you're willing to take a go at it, I'd be happy to provide guidance! |
Thanks a lot for all the information! If I had infinite time, this project would certainly be on my list - but the way the world works, I can't make any promises for when and if I will have time for any additional projects... |
To complement this, sometime, even when there is only one message in the conversation, the loading basically never ends. I think this is triggered when the message contains some html. |
I view emails with HTML all the time and the loading is fine. If you can On 11/30/2015 11:27 AM, Gabriel Radanne wrote:
|
Hi, Anyway, it became kind of annoying so I deactivated the extension to see the difference. Anyway, I have been using this extension for a few years, and very happy with it (apart from this issue), so many thanks for that! |
Hello all, I'm using TB (52.6.0 (64 bits)) at work with Conversation (2.13.4) and I'm facing same issue as the second point described by @protz at top of this thread. Thousand mails after thousand mails in my folders (more than 11000), displaying a conversation takes more and more time averagely speaking. For example, it frequently takes 9 sec. Did you guys found out a way to fix this behaviour ? Otherwise I will sadly be forced to disable this plugin after passing over a limit some day... I also see bug #1013 which really seems to be a consequence. I take the opportunity to thank you so much guys for the new UI which get near what I got with my ugly local css patch in the past. The only thing I miss is buttons instead of HTML links, but I can deal with it :) |
The same here, TB (52.8.0 (64 bits)) with conversation (2.13.4). Displaying a conversation with 60 mails could take ~15s, this make my computer (Intel® Core™ i7-7600U CPU @ 2.80GHz × 4 + 16 Gio) overloaded ... (almost all the core to 100%, fan speed to max) Except this issue this extension is really great ! I didn't understand why this is not the default UI for Thunderbird. |
I believe this is now much improved after the recent rewrite of Conversations. We've changed how the display mechanisms work and that seems to help a lot. We're still waiting to receive all the messages from gloda as per @protz's previous comment, but overall I believe this is better. If it is still bad for people, I'd appreciate knowing the numbers of messages and time to display. |
Sorry, I can't tell you because I moved to other company where I don't use Thunderbird... Hope anyone else can give you more stats. |
I've not had more responses, so I'll close it out for now. I think it is improved, though obviously could get better still, and we'll be able to hopefully work towards that more once the current writes are done. |
When I click a message, even one that has no other message in its conversation, showing that message takes way longer than it does with the plain Thunderbird view. The latter is instantaneous, while the plugin slows it down to at least a tenth of a seconds until the message is first shown, and then another tenth of a second until it stops re-flowing the auto-reply boxes (they always hop around when switching threads). This is particularly noticeable when scrolling through a folder of a mailing-list, where I'm not really interested in most messages and just go through them by pressing "n" repeatedly. Now I have to actively wait after every "n" to avoid skipping messages.
Once the displayed conversation contains more than a single message, showing it can easily take more than a second (I'd estimate that happens around 5 messages/thread). With 10 messages, it's already 2-3 seconds.
The text was updated successfully, but these errors were encountered: