GNOME Bugzilla – Bug 586882
evolution takes a long time to start up
Last modified: 2017-11-20 21:12:25 UTC
Usually only after having to force it down with evolution --force-shutdown. It seems it takes many many minutes going through the .evolution/mail/vfolder/folders.db database. Mine here is: 472,728,576. But this is obviously something that is not scaling.
One obvious problem here is that Evo doesn't do vacuum, which is bad and pending implementation :/. There should be a scheme to do auto vacuum once in a month or so. Can you see, if 'sqlite3 ~/.evolution/mail/vfolder/folders.db "vacuum;"' help improve the situation? If so then I can finalize its that.
So, I did a vacuum. It took 10 minutes. And even after that, starting evolution took minutes after the shell appeared before e-mail was usable. This change to sqlite for scalability doesn't seem to be working too well.
Any update or thoughts on this? Having to wait over 10 minutes for evo to start after it has crashed is just unusable. Where's the performance enhancement this sqlite migration was supposed to provide?
Can you get some glances of 'thread apply all bt' 4-5 traces while starting up evo? in some good intervals if its 10minutues.
Created attachment 138536 [details] stack traces while starting after crash Some stack traces while Evo takes many, many minutes starting up after a crash.
(In reply to comment #4) > Can you get some glances of 'thread apply all bt' 4-5 traces while starting up > evo? in some good intervals if its 10minutues. Attached. FWIW, it seems to spend most time preparing vfolders for news groups. I have one vfolder that aggregates all of the NNTP groups I'm subscribed to via gmane. If you can trust the article count in the left pane these days, the largest vfolder has 406K unread NNTP articles.
I think most of the time is spent in "newsgroup/all" vfolder. Is that the one you said?
(In reply to comment #7) > I think most of the time is spent in "newsgroup/all" vfolder. Is that the one > you said? 'Tis indeed.
Anything more on this bug?
Can you please check again whether this issue still happens in Evolution 2.32.2 or 3.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!