On Sat, 07 Apr 2018 14:42:49 +0100
Mick <michaelkintz...@gmail.com> wrote:
On Saturday, 7 April 2018 14:35:27 BST Floyd Anderson wrote:
Hi Mick,
On Sat, 07 Apr 2018 11:21:23 +0100
Mick <michaelkintz...@gmail.com> wrote:
>So far I had been using gdbm, but I now see that emerge also added lmdb.
Same here, so I gave lmdb a try as hcache backend.
>Which one is best to use? What have you chosen?
I assume you mean for speed? I don’t know and it may become very
academic to answer this. But you can find some none Mutt-specific
benchmark results on NeoMutt’s website [1].
Note, the mentioned benchmark page say:
“[…] you’ll need a reasonable large number of
messages – >50k – to see anything interesting”
Using lmdb as backend, I do not realise any differences over gdbm within
Mutt respectively NeoMutt and I doubt one really can (without measuring
it exactly – which I haven’t done yet).
References:
[1] <https://www.neomutt.org/contrib/hcache-bench>
Thanks Floyd, good information.
I also switched to lmdb now and updated my use flags accordingly for mutt. I
see neomutt gaining traction, but I am still running mutt here. Is there a
benefit from switching?
I think yes but I’m also using both here. Mutt for testing different
behaviour (sometimes issues) of NeoMutt and NeoMutt as as my day-to-day
mail client workhorse.
The main reason for my switch to NeoMutt was that I’ve had no luck with
colourisation in Mutt (nearly two years ago). TBH, afterwards I realised
that the problem was sitting in front of the screen and used
sys-libs/slang instead of sys-libs/ncurses), so no reason for a switch.
But I like the faster development/release cycle, the goal to clean up
the 20 years old code base and some features [1] of NeoMutt, e.g.
Lua-scripting, sidebar; which sometimes find their way into Mutt. I have
no experiences contributing patches to Mutt but regarded to NeoMutt, it
meet my expectations and that is fun.
Back to the topic, with a another example. As far as I can tell you
cannot change the hcache backend without recompiling Mutt where NeoMutt
implements the ‘$header_cache_backend’ configuration variable for.
But in the end I can only say forget all things above, I’m only more
familiar with NeoMutt than with Mutt.
References:
[1] <https://www.neomutt.org/feature.html>
--
Regards,
floyd
