Performance-issues with large threads

Mark Walters markwalters1009 at gmail.com
Tue Jul 23 05:53:38 PDT 2013


Hi

Sorry this will be a big list of questions but they might help narrow
down the problem. 

How long does 

notmuch show --format=json thread:thread-id  > /dev/null

take? Is it much faster after the first run? What about the same with
the added cli option --body=false?

(you probably want something like  echo 3 > /proc/sys/vm/drop_caches
between batches of runs)

Do the messages have html parts?

Also what disk are you using (and does it have any other significant
activity happening)? And what version of notmuch are you using?

Best wishes

Mark






Franz Fellner <alpine.art.de at gmail.com> writes:

> Hi,
>
> "Large" in the context of this issue is >20 replies, I have to wait ~1 sec until the thread shows up. With larger conversations it get's worse (a bug report on bugs.kde.org with ~400 replies takes ~13 secs. to load).
> This is due to the fact, that notmuch-{vim,emacs} load the complete mail including the body.
> ner does a great job here, it loads all headers but only the body of the first unread mail, resulting in instant loading even of gigantic conversations. It would be terrific to see something like that, at least in my favored vim-client ;)
>
> Thx
> Franz
> _______________________________________________
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch


More information about the notmuch mailing list