unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Kim Minh Kaplan <kimminh.kaplan+nomuch@afnic.fr>
To: notmuch@notmuchmail.org
Cc: Don Zickus <dzickus@redhat.com>
Subject: Re: performance problems with notmuch new
Date: Mon, 20 Apr 2020 15:04:30 +0000	[thread overview]
Message-ID: <875zdukxkx.fsf@kakou.tech.prive.nic.fr> (raw)
In-Reply-To: <1587211167-ner-6.432@LappyL520>

Franz Fellner writes:

> 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?

Hello,

I had a similar performance issue working with a very large email set
(in the million count). Amongst those, I have crons that run about every
minute and email back a report, mostly identical every time with some
thousands words.

Apparently indexing many times mostly identical emails triggers a
pathological behaviour. Moving these email out of my mail directories
brought back acceptable performances. We are speaking in the 10,000 to
100,000 files here.

Kim Minh.


> 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...

      parent reply	other threads:[~2020-04-20 15:04 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
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 [this message]

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=875zdukxkx.fsf@kakou.tech.prive.nic.fr \
    --to=kimminh.kaplan+nomuch@afnic.fr \
    --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).