Sorry didn't follow that link.
> I'm guessing my "non-changing" maildir content is possibly less than
> half of my total maildir content. If the performance scales linearly,
> then at best that makes the performance different 7x instead of 15x.
> Maybe there's more tricks I can employ to reduce this difference even
> further?
You have a mailbox with 500,000 messages that needs to be frequently updated and can't archive the bulk of it? Then, no, mu probably isn't the right tool for this setup.
I have 200k messages but on Jan 1 put the 10k emails from 2014 into a 2014_archive folder, index it, and then add the .noupdate file. I can search and read them almost instantly, and they show up appropriately in all views including ongoing threads which include those messages. Since I get/keep about 10k messages per year, half-way through 2015 I am now indexing 5000 messages. This takes ~1 second. In December my updates will take ~2s.
$ time mu index
indexing messages under /Users/mankoff/Maildir [/Users/mankoff/.mu/xapian]
| processing mail; processed: 5775; updated/new: 0, cleaned-up: 0
cleaning up messages [/Users/mankoff/.mu/xapian]
- processing mail; processed: 118607; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 118607 msg/s
\ processing mail; processed: 118607; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 118607 msg/s
1.01 real 0.39 user 0.37 sys
>> There is mention of it. Try google. BUT that is the wrong file. You
>> want .noupdate, not .noindex.
>
> Ok, thanks. '.noindex' was referenced in original post, but I'm
> assuming '.noindex' was incorrect (and has no other use/function), and
> I'll use '.noupdate' instead.
Yes. .noindex was a typo on my part in first message. It has other uses.
-k.