<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/performance-test/version.sh, branch 0.35_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.35_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.35_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2013-12-09T20:00:38Z</updated>
<entry>
<title>perf-test: bump version to 0.4, use manifest files</title>
<updated>2013-12-09T20:00:38Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2013-12-01T03:00:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2de8ce9b37bfaed7c5a962a5316dbc9c9c3cb2c8'/>
<id>urn:sha1:2de8ce9b37bfaed7c5a962a5316dbc9c9c3cb2c8</id>
<content type='text'>
The new revision of the performance test includes manifests for each corpus,
so update the support library to use these manifests at the same time.
</content>
</entry>
<entry>
<title>perf-test: bump corpus version to 0.3</title>
<updated>2012-12-15T12:17:58Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-12-04T02:58:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5f8e37691297135d58839d4d8e683670b9f4eef2'/>
<id>urn:sha1:5f8e37691297135d58839d4d8e683670b9f4eef2</id>
<content type='text'>
The new version ships with some tags, and an updated archive of the
notmuch mailing list.
</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>
