There was some previous discussion of the speed of "mu index" 
here: https://groups.google.com/forum/#!msg/mu-discuss/-K5O1uoP7bQ/n49EreaQtlAJ

I'm now on an SSD (MacBook Pro w/ 1 TB SSD primary and the 1TB platter now 
in the CD-rom bay). I really REALLY like mu4e, but it is unusably slow on 
OS X and I don't think I can keep using it in the current state. I'm happy 
to try to help debug this, and hope it gets solved so I can make this my 
primary mail client. If I try to run mu outside of emacs so that the 
slowness isn't directly affecting a program I'm actively using, I get the 
locking errors since mu4e is also running. If I run it in emacs with (setq 
mu4e-update-interval 300), then when I try to do something during the time 
that mu is indexing, everything gets messed up, and mu4e does not seem to 
recover gracefully (i.e. maildirs don't properly open, or searches return 
nothing, until I kill and restart mu).

Based on the earlier thread where Dirk posted his timings, it seems to be 
an OS X issue? I'm using an SSD, have 8 GB of RAM, and an old CPU (2.26 
GHz).

Perhaps it is not a mu-specific problem, since it takes 2 seconds just to 
list the maildir folder. This is after repeat runs, so I am taking 
advantage of caches:

$ time ls -R1 ~/Maildir > /dev/null
real    0m1.744s
user    0m1.118s
sys     0m0.080s

$ ls -R1 Maildir/|wc -l
  106086

Although mu index only searches 60k files, since 40k have a ".noupdate" 

And after repeated runs of mu index with no new mail:

$ time mu index
indexing messages under /Users/mankoff/Maildir [/Users/mankoff/.mu/xapian]
| processing mail; processed: 61575; updated/new: 0, cleaned-up: 0
cleaning up messages [/Users/mankoff/.mu/xapian]
- processing mail; processed: 61609; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 61609 msg/s
\ processing mail; processed: 61609; updated/new: 0, cleaned-up: 0
elapsed: 6 second(s), ~ 10268 msg/s

real    0m5.621s
user    0m0.966s
sys     0m2.384s

$ mu --version
mu (mail indexer/searcher) version 0.9.9.5

and xapian 1.2.17.

Searching is also much slower than Dirk's earlier report, although I don't 
mind waiting a few seconds for a search:

$ time mu find hello |wc -l
    2555
real    0m1.031s
user    0m0.165s
sys     0m0.287s


Please help (if possible). If not I'll be forced to go back to alpine, 
which is great, except it doesn't search well, and doesn't integrate with 
Org...

  -k.


-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to