From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org, xapian-discuss@lists.xapian.org
Subject: Re: slowdown in notmuch perf suite with xapian 1.3.5
In-Reply-To: <20160407232537.GB29434@survex.com>
References: <87twjd639d.fsf@zancas.localnet>
 <20160407232537.GB29434@survex.com>
User-Agent: Notmuch/0.21+99~gd93d377 (http://notmuchmail.org) Emacs/24.5.1
 (x86_64-pc-linux-gnu)
Date: Thu, 07 Apr 2016 21:40:59 -0300
Message-ID: <87h9fd53vo.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

Olly Betts <olly@survex.com> writes:

>
> So the T00-new.sh numbers make sense - there's more work to do, and
> we need to read existing positional data more to insert the new stuff,
> so the increased reads and writes make sense.
>
> But guessing at what the other two tests do, I wouldn't expect them to
> be affected by this.

The non-optimized-away cases of T02-tag just adding and deleting terms
to each document with term Tmail

> I'm also a bit puzzled by how glass can manage not to read any data
> for "dump *", and several tests seem to not read or write anything
> for either backend.  What exactly are the "In/Out" numbers?

that's just the output from /usr/bin/time -f '%e\t%U\t%S\t%M\t%I/%O'

The manual describes them as "number of file system
inputs/outputs". From looking at the source, they correspond to
ru_inblock and ru_oublock fields from the getrusage call. AFAIU, that
means the number of non-cached read/writes.

d