<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/performance-test/T02-tag.sh, 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>2024-04-05T10:33:41Z</updated>
<entry>
<title>perf-test/tag: add maildir sync tests</title>
<updated>2024-04-05T10:33:41Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2023-09-30T11:40:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=de234097048c82be74dfb8ec265ac03704308a90'/>
<id>urn:sha1:de234097048c82be74dfb8ec265ac03704308a90</id>
<content type='text'>
Today someone asked me the (reasonable) question of how much
performance impact there is from synching tags to maildir flags. It
turns out it is noticeable, about a 50% overhead compared to
non-synched tags (according to these tests).  In practice I don't know
if it's a big problem for users, since I don't know what fraction of
tagging operations involve "special" tags.
</content>
</entry>
<entry>
<title>perf-tests: #!/bin/bash -&gt; #!/usr/bin/env bash</title>
<updated>2019-06-07T10:59:56Z</updated>
<author>
<name>William Casarin</name>
<email>jb55@jb55.com</email>
</author>
<published>2019-05-31T18:32:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5f22d16273ef0d42fc42303087a588efeeb6d7c1'/>
<id>urn:sha1:5f22d16273ef0d42fc42303087a588efeeb6d7c1</id>
<content type='text'>
I couldn't run the performance tests on my machines due to a hardcoded
bash path. Use env for finding bash in weird systems like NixOS.

Signed-off-by: William Casarin &lt;jb55@jb55.com&gt;
</content>
</entry>
<entry>
<title>perf-test: use $(dirname "$0") for sourcing perf-test-lib.sh</title>
<updated>2017-10-20T22:53:14Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-25T20:38:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fd36ae9f514520e85d9e43d4aa08263b3a5a8d3e'/>
<id>urn:sha1:fd36ae9f514520e85d9e43d4aa08263b3a5a8d3e</id>
<content type='text'>
Don't assume the tests are always run from within the source tree.
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
<entry>
<title>perf-test: rename time tests to have .sh suffix</title>
<updated>2013-05-16T01:23:29Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2013-05-15T10:40:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0eab376658689469c5427d1b2c292de62e009aee'/>
<id>urn:sha1:0eab376658689469c5427d1b2c292de62e009aee</id>
<content type='text'>
This will simplify notmuch time tests
</content>
</entry>
</feed>
