<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/performance-test/basic, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-12-15T12:29:08Z</updated>
<entry>
<title>perf-test: split basic into 00-new, 01-dump-restore, and 02-tag</title>
<updated>2012-12-15T12:29:08Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-12-06T01:34:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=51b0f8ff3373fe744691b4836f4ee85919e3ec4a'/>
<id>urn:sha1:51b0f8ff3373fe744691b4836f4ee85919e3ec4a</id>
<content type='text'>
We use the new "time_start" function to restore the database from cache
if possible.
</content>
</entry>
<entry>
<title>perf-test: add caching of xapian database</title>
<updated>2012-12-15T12:17:58Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-12-03T12:48:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ceaf5ca6c02e494eee5b9b9aa955459b3cd29471'/>
<id>urn:sha1:ceaf5ca6c02e494eee5b9b9aa955459b3cd29471</id>
<content type='text'>
The caching and uncaching seem to be necessarily manual, as timing the
initial notmuch new is one of our goals with this suite.
</content>
</entry>
<entry>
<title>test: initial performance testing infrastructure</title>
<updated>2012-11-26T12:39:21Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-11-17T16:28:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7beeb8c88a014ecbc53d8241f10683b3c4c16228'/>
<id>urn:sha1:7beeb8c88a014ecbc53d8241f10683b3c4c16228</id>
<content type='text'>
This is not near as fancy as as the unit tests, on the theory that
the code should typically be crashing when performance tuning.
Nonetheless, there is plenty of room for improvement.  Several more of
the pieces of the test infrastructure (e.g. the option parsing) could
be factored out into test/test-lib-common.sh
</content>
</entry>
</feed>
