Continuing on a bit the search discussion, I'm playing around more with
notmuch now, and I'm wondering if this is something on my side, or if
it's a problem with the implementation of notmuch, but notmuch takes a
very long time to load the mail lists on change to folder, or when
returning from a query. Is this to be expected, or is there something I
can do to rectify this?
Running on Arch Linux with a pretty straight-forward setup:
[proton-notmuch]
source = notmuch://~/mail
maildir-store = ~/mail
query-map = ~/.config/aerc/map.conf
outgoing = smtps://kennethflak%40protonmail.com:xxxxxxxxxxxxxxxxxxxxxxxx@127.0.0.1:1025
default = INBOX
from = Kenneth Flak <kennethflak@protonmail.com>
--
Roosna & Flak - Contemporary Dance & Music
Web: roosnaflak.com
Code: {github,gitlab}.com/kflak
Mastodon: @kf@sonomu.club
Hey Kenneth,
2024. máj. 9. 6:24:09 Kenneth Flak <kennethflak@protonmail.com>:
> Continuing on a bit the search discussion, I'm playing around more with> notmuch now, and I'm wondering if this is something on my side, or if> it's a problem with the implementation of notmuch, but notmuch takes a> very long time to load the mail lists on change to folder, or when> returning from a query. Is this to be expected, or is there something I> can do to rectify this?>
I think notmuch has some issues with performance, but I havent had the
time to investigate.. Are you running latest master?
It would probably be quite helpful, if you could do some performance
testing.
perf record -gp $(pidof aerc)
and flamegraph: https://github.com/brendangregg/FlameGraph
Best,
Bence
> Running on Arch Linux with a pretty straight-forward setup:>> [proton-notmuch]> source = notmuch://~/mail> maildir-store = ~/mail> query-map = ~/.config/aerc/map.conf> outgoing = > smtps://kennethflak%40protonmail.com:xxxxxxxxxxxxxxxxxxxxxxxx@127.0.0.1:1025> default = INBOX> from = Kenneth Flak <kennethflak@protonmail.com>>>> --> Roosna & Flak - Contemporary Dance & Music> Web: roosnaflak.com> Code: {github,gitlab}.com/kflak> Mastodon: @kf@sonomu.club
> It would probably be quite helpful, if you could do some performance> testing.>> perf record -gp $(pidof aerc)>> and flamegraph: https://github.com/brendangregg/FlameGraph>
Hi Bence,
Would be very happy to, but I have no clue how to use those tools, nor
how to make sense of the data generated. Should I just run the perf
command while doing the stuff in notmuch that takes a long time? What to
do with the generated data file?
Best,
Kenneth
On Sat May 11, 2024 at 20:54, Kenneth Flak <kennethflak@protonmail.com> wrote:
> > It would probably be quite helpful, if you could do some performance> > testing.> >> > perf record -gp $(pidof aerc)> >> > and flamegraph: https://github.com/brendangregg/FlameGraph> >> Hi Bence,>> Would be very happy to, but I have no clue how to use those tools, nor> how to make sense of the data generated. Should I just run the perf> command while doing the stuff in notmuch that takes a long time? What to> do with the generated data file?
LOL, I literally learned yesterday from Robin, so no expert, but
- you start aerc
- in another terminal you run the perf command
and then apparently `perf script report flamegraph` this may work on Linux?
It'll generate something like this:
https://www.brendangregg.com/flamegraphs.html which you can send here so the
actually experts can take a look :D
Thanks,
Bence
--
+36305425054
bence.ferdinandy.com
>> LOL, I literally learned yesterday from Robin, so no expert, but>> - you start aerc> - in another terminal you run the perf command>> and then apparently `perf script report flamegraph` this may work on Linux?>> It'll generate something like this:> https://www.brendangregg.com/flamegraphs.html which you can send here so the> actually experts can take a look :D>
Okidoki, here's the resulting html file:
https://paste.rs/zP3aM
Hopefully the gurus can glean something from it :-)
Kenneth