From: Franz Fellner <alpine.art.de@gmail.com>
To: Don Zickus <dzickus@redhat.com>, notmuch@notmuchmail.org
Subject: Re: performance problems with notmuch new
Date: Sat, 18 Apr 2020 14:59:27 +0300 [thread overview]
Message-ID: <1587211167-ner-6.432@LappyL520> (raw)
In-Reply-To: <20200415150801.h2mazyo37sspvech@redhat.com>
I also suffer from bad performance of notmuch new.
I used notmuch some years ago and notmuch new always felt instantanious.
Had to stop using it because internet was too slow to sync my mails :/
Now (with better internet and a completely new setup using mbsync) indexing one mail takes at least 10 seconds, sometimes even more.
It can go into minutes when I get lots of mail (~30...).
When I run it after a reboot I can have breakfast while notmuch starts up...
This is all on spinning rust. I thought of getting an SSD but not in the near future.
What I observe during that time: notmuch doesn't really need much CPU.
iotop shows constant read and write with extremely low rates, under 1MB/sec.
So I think it might be an issue in xapian?
If there is anything I can do to help debug this please tell me
Franz
P.S.:
@David: Sorry for writing only to you.
GMail web interface only added you as recipient and not the list...
On Wed Apr 15 11:08:01 2020, Don Zickus <dzickus@redhat.com> wrote:
> Hi,
>
> I have noticed my 'notmuch new' command seems awfully slow, maybe 10-20
> emails / second on large batches. It goes quick for the first few hundred
> (maybe close to 100/second), then quickly slows down to about 10/second
> after processing the first 500 or so.
>
> I am guessing that isn't an expected behaviour. So I am trying to figure
> out a good way to analyze and debug this? This could be a problem with my
> fedora distro or laptop. I just don't know where to look.
>
> Tips for debugging this?
>
> I ran the notmuch performance/time-test, but after 15 minutes of waiting for
> the initial notmuch new to finish, I gave up and aborted.
>
> I am using 'glass' for my xapian storage if that helps.
>
> Help?
>
> Cheers,
> Don
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
>
>
--
next prev parent reply other threads:[~2020-04-18 11:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 15:08 performance problems with notmuch new Don Zickus
2020-04-15 16:01 ` David Bremner
2020-04-15 17:31 ` Don Zickus
2020-04-15 20:29 ` David Bremner
2020-04-20 15:25 ` Don Zickus
2020-04-24 10:36 ` David Bremner
2020-04-24 19:05 ` Don Zickus
2020-04-24 23:07 ` David Bremner
2020-04-27 12:48 ` Don Zickus
2020-04-27 12:56 ` David Bremner
2020-04-20 14:31 ` David Bremner
2020-04-20 16:26 ` Don Zickus
2020-04-18 11:59 ` Franz Fellner [this message]
2020-04-20 14:36 ` David Bremner
2020-04-22 10:46 ` Franz Fellner
2020-04-22 23:21 ` Olly Betts
2020-04-24 18:35 ` Franz Fellner
2020-04-24 23:13 ` David Bremner
2020-04-29 9:30 ` Eric Wong
2020-04-20 15:04 ` Kim Minh Kaplan
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=1587211167-ner-6.432@LappyL520 \
--to=alpine.art.de@gmail.com \
--cc=dzickus@redhat.com \
--cc=notmuch@notmuchmail.org \
/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).