From: David Bremner <david@tethera.net>
To: Don Zickus <dzickus@redhat.com>
Cc: notmuch@notmuchmail.org
Subject: Re: performance problems with notmuch new
Date: Wed, 15 Apr 2020 17:29:13 -0300 [thread overview]
Message-ID: <87y2qwsdba.fsf@tethera.net> (raw)
In-Reply-To: <20200415173138.rn3ubtxo6mkracss@redhat.com>
Don Zickus <dzickus@redhat.com> writes:
>> runs in about 30s here (i7 4770 / SSD). Replacing --small with --medium
>> takes about 10M (so a superlinear slowdown in wall clock time, since
>> that represents a 10x scale-up in the corpus size.).
>
> Hmm, for me --small was 35s and --medium was 32 minutes. This is on a
> i7-9750H / nvme. I would expect numbers similar to yours.
I did another few tests test for --medium and they all take 7-9 minutes,
depending what else is going on on the machine.
Here's my breakdown of times (unfortunately a bit of hand editing is
needed to clean up the warnings)
performance-test/notmuch-time-test --medium
T00-new.sh: Testing notmuch new [0.4 medium]
Wall(s) Usr(s) Sys(s) Res(K) In/Out(512B)
Initial notmuch new 66.29 62.22 2.82 241148 0/1089784
notmuch new #2 0.03 0.00 0.00 9864 0/160
notmuch new #3 0.00 0.00 0.00 9292 0/8
notmuch new #4 0.00 0.00 0.00 9556 0/8
notmuch new #5 0.00 0.00 0.00 9396 0/8
notmuch new #6 0.00 0.00 0.00 9316 0/8
new (7500 mv) 49.02 35.88 12.59 185152 0/392720
new (7500 mv back) 59.41 43.04 15.88 185888 0/413824
new (7500 cp) 36.09 26.55 9.02 182160 0/411840
T01-dump-restore.sh: Testing dump and restore [0.4 medium]
Wall(s) Usr(s) Sys(s) Res(K) In/Out(512B)
load nmbug tags 5.37 2.09 1.63 12172 0/31864
dump * 0.63 0.58 0.04 11756 0/4344
restore * 0.72 0.65 0.06 9572 0/0
T02-tag.sh: Testing tagging [0.4 medium]
Wall(s) Usr(s) Sys(s) Res(K) In/Out(512B)
tag * +new_tag 54.45 31.93 20.26 86380 8/250512
tag * +existing_tag 0.00 0.00 0.00 9396 0/0
tag * -existing_tag 46.73 26.07 20.08 20580 0/284248
tag * -missing_tag 0.00 0.00 0.00 9316 0/0
T03-reindex.sh: Testing reindexing [0.4 medium]
Wall(s) Usr(s) Sys(s) Res(K) In/Out(512B)
reindex * 78.39 63.06 14.31 229204 0/546136
reindex * 70.52 56.68 13.12 223980 0/333608
reindex * 78.02 62.61 14.92 225160 0/374424
T04-thread-subquery.sh: Testing thread subqueries [0.4 medium]
Wall(s) Usr(s) Sys(s) Res(K) In/Out(512B)
search thread:{} ... 0.37 0.33 0.04 26508 0/24
search thread:{} ... 0.38 0.33 0.04 23592 0/24
search thread:{} ... 0.37 0.34 0.03 26612 0/24
415.28user 128.24system 9:13.07elapsed 98%CPU (0avgtext+0avgdata 241148maxresident)k
8inputs+7294896outputs (0major+458590minor)pagefaults 0swaps
next prev parent reply other threads:[~2020-04-15 20:29 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 [this message]
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
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=87y2qwsdba.fsf@tethera.net \
--to=david@tethera.net \
--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).