Mu4e performance issues on macOS (1.0 related?)

[Jack Baty]

I've noticed a significant performance degradation while using Mu4e recently. Unfortunately I can't tie it directly to the 1.0 upgrade but it began about the same time.

A few things have started taking much longer:

- There is a several second delay after hitting R for Reply before the new edit buffer is displayed.
- There is a 10+ second delay after running [U]pdate between when the "Indexing completed..." message is shown and when the "Contacts received" message is shown in the mini-buffer. That's quite a long time.
- When first [j]ump-ing to my Inbox, a "Searching..." message is sometimes shown before the messages appear.

I'm running a similar (if not identical) configuration and mailboxes on (Manjaro) Linux and all of the above happen nearly instantly, like they used to on my Mac

Emacs 25.3.1 and spacemacs "develop" branch (as of today).

Mac: mu4e - mu for emacs version 1.0 C
Linux: mu4e - mu for emacs version 0.9.18 C

I'd try upgrading or downgrading but frankly getting mu/mu4e running has been tricky for me and I'd rather not tamper with it until absolutely necessary :).

Of course this could also be completely unrelated to mu and so I apologize if I haven't narrowed things down well enough. I'm hoping to learn at least where to start looking.

Thanks

Jack

[Eduardo Mercovich]

Hi Jack.

> I've noticed a significant performance degradation while using

> Mu4e recently. [...] getting mu/mu4e running has been tricky for

> me and I'd rather not tamper with it until absolutely necessary
> :).

Totally undestrandable, at least for newbies like me.

> Of course this could also be completely unrelated to mu and so I
> apologize if I haven't narrowed things down well enough. I'm
> hoping to learn at least where to start looking.

Just to start, did you noticed any other performance degradation
in your emacsverse? Or just mu4e?
Is it possible to star emacs without your settings and just load
mu4e to check if it still happens?


--
Eduardo Mercovich

Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
(Anónimo)

[Jack Baty]

Just to start, did you noticed any other performance degradation
in your emacsverse? Or just mu4e?
Is it possible to star emacs without your settings and just load
mu4e to check if it still happens?

There may be some general slowdowns but nothing so severe that it jumped out at me. I'll spend some time this weekend trying to isolate things. Thanks!

[Dirk-Jan C. Binnema]

On Friday Feb 09 2018, Jack Baty wrote:

> I've noticed a significant performance degradation while using Mu4e
> recently. Unfortunately I can't tie it directly to the 1.0 upgrade but it

> began *about *the same time.

>
> A few things have started taking much longer:
>
> - There is a several second delay after hitting R for Reply before the new
> edit buffer is displayed.
> - There is a 10+ second delay after running [U]pdate between when the
> "Indexing completed..." message is shown and when the "Contacts received"
> message is shown in the mini-buffer. That's quite a long time.
> - When first [j]ump-ing to my Inbox, a "Searching..." message is sometimes
> shown before the messages appear.
>
> I'm running a similar (if not identical) configuration and mailboxes on
> (Manjaro) Linux and all of the above happen nearly instantly, like they
> used to on my Mac
>
> Emacs 25.3.1 and spacemacs "develop" branch (as of today).
>
> Mac: mu4e - mu for emacs version 1.0 C
> Linux: mu4e - mu for emacs version 0.9.18 C
>
> I'd try upgrading or downgrading but frankly getting mu/mu4e running has
> been tricky for me and I'd rather not tamper with it until absolutely
> necessary :).
>
> Of course this could also be completely unrelated to mu and so I apologize
> if I haven't narrowed things down well enough. I'm hoping to learn at least
> where to start looking.

Don't think here's anything between 0.9.18 and 1.0 that could explain
the difference, I think. You could check the `Speeding up indexing"
section in the manual, that might have some hints.

Does command-line `mu' have similar problems?

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

[Charles-H. Schulz]

Hello,

I had these problems before the 1.0 but I did not really tweak the indexing config and I have a pretty heavy set of mailboxes my runs on, somewhere above 10Gb.

To me it is not really slower than any graphical client , certainly faster than Gnus and probably related to Emacs itself in part.

Best,

Charles.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema                  Helsinki, Finland
e:dj...@djcbsoftware.nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

--
You received this message because you are subscribed to the Google Groups "mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mu-discuss+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jack Baty]

I may have found the problem. After recently copying my ~/Mail directory for use on my Linux laptop, all of my messages were shown as Unread. (see https://groups.google.com/forum/#!topic/mu-discuss/1hL0oJXidiY).

I had `mu4e-enable-mode-line` enabled and what I think was happening is that the query used by mu4e-alert to find "interesting" (aka unread) messages was taking a long time to run and was somehow blocking things. Setting `mu4e-enable-mode-line` to nil has sped things up dramatically.

For example, the delay between showing "Indexing complete..." and "Contacts received..." has gone from >10 seconds to <3 seconds. There's also no longer a delay between hitting R to reply and the appearance of the new edit buffer.

Could this have been it? If so, I'll start a new thread asking how to mark all messages read (and not have to do it 500 at a time).

[Dirk-Jan C. Binnema]

Perhaps. Good that it fixed the problem!

`mu4e-enable-mode-line' is not part of mu4e though; you must be getting
that from some other package (spacemacs?). It's a bit confusing they're
using the same namespace.

The general advise when something's doesn't work as expected: try to
reproduce with an as vanilla as possible mu4e, without other packages
that might influence things.

[Jack Baty]

 

`mu4e-enable-mode-line' is not part of mu4e though; you must be getting
that from some other package (spacemacs?). It's a bit confusing they're
using the same namespace.

It's part of "mu4e-alert" https://github.com/iqbalansari/mu4e-alert and is configured as part of the Spacemacs layer.