unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Dan Čermák" <dan.cermak@posteo.net>
To: sfischme@uwaterloo.ca
Cc: notmuch@notmuchmail.org
Subject: Re: Debugging slow down over time
Date: Wed, 11 Nov 2020 10:47:12 +0100	[thread overview]
Message-ID: <87sg9g2pjz.fsf@cgc-instruments.com> (raw)
In-Reply-To: <877dqtkqs9.fsf@uwaterloo.ca>


[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]

Hi Sebastian,

Sebastian Fischmeister <sfischme@uwaterloo.ca> writes:

> Hi,
>
> For some time already I experience a slowdown of the emacs notmuch interface over time. After using emacs with notmuch for a day or two, loading the inbox tree view (a search on tag:inbox) takes a significant amount of time to build the view. When I quite and restart emacs, the view loads instantly again.
>
> Do you have any suggestions on how to debug this issue other than
> removing all customizations?

Unfortunately no, but I have observed this issue as well. What sometimes
appeared to help is to manually trigger a garbage collection.

I must admit that I have not suffered from this recently though and it
might have disappeared when I added
--8<---------------cut here---------------start------------->8---
(setq helm-ff-keep-cached-candidates nil)
--8<---------------cut here---------------end--------------->8---
to my init.el to work around https://issues.guix.gnu.org/43406

In case you are using helm, you could give that a try.


Cheers,

Dan

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2020-11-11  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 18:31 Debugging slow down over time Sebastian Fischmeister
2020-11-11  9:47 ` Dan Čermák [this message]
2020-11-12  1:06   ` Sebastian Fischmeister
2020-11-11 14:20 ` Jonas Bernoulli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sg9g2pjz.fsf@cgc-instruments.com \
    --to=dan.cermak@posteo.net \
    --cc=notmuch@notmuchmail.org \
    --cc=sfischme@uwaterloo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).