notmuch/performance-test/T02-tag.sh

#!/usr/bin/env bash

test_description='tagging'

. $(dirname "$0")/perf-test-lib.sh || exit 1

time_start

time_run 'tag * +new_tag' "notmuch tag +new_tag '*'"
time_run 'tag * +existing_tag' "notmuch tag +new_tag '*'"
time_run 'tag * -existing_tag' "notmuch tag -new_tag '*'"
time_run 'tag * -missing_tag' "notmuch tag -new_tag '*'"

time_run 'tag * +maildir_flag F' "notmuch tag +flagged '*'"
time_run 'tag * -maildir_flag F' "notmuch tag -flagged '*'"
time_run 'tag * +maildir_flag P' "notmuch tag +passed '*'"
time_run 'tag * -maildir_flag P' "notmuch tag -passed '*'"
time_run 'tag * +maildir_flag D' "notmuch tag +draft '*'"
time_run 'tag * -maildir_flag D' "notmuch tag -draft '*'"
time_run 'tag * +maildir_flag S' "notmuch tag -unread '*'"
time_run 'tag * -maildir_flag S' "notmuch tag +unread '*'"

time_done
perf-tests: #!/bin/bash -> #!/usr/bin/env bash 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 <jb55@jb55.com> 2019-05-31 11:32:50 -07:00			`#!/usr/bin/env bash`
perf-test: split basic into 00-new, 01-dump-restore, and 02-tag We use the new "time_start" function to restore the database from cache if possible. 2012-12-05 21:34:30 -04:00
			`test_description='tagging'`

perf-test: use $(dirname "$0") for sourcing perf-test-lib.sh Don't assume the tests are always run from within the source tree. 2017-09-25 23:38:20 +03:00			`. $(dirname "$0")/perf-test-lib.sh \|\| exit 1`
perf-test: split basic into 00-new, 01-dump-restore, and 02-tag We use the new "time_start" function to restore the database from cache if possible. 2012-12-05 21:34:30 -04:00
			`time_start`

			`time_run 'tag * +new_tag' "notmuch tag +new_tag '*'"`
			`time_run 'tag * +existing_tag' "notmuch tag +new_tag '*'"`
			`time_run 'tag * -existing_tag' "notmuch tag -new_tag '*'"`
			`time_run 'tag * -missing_tag' "notmuch tag -new_tag '*'"`

perf-test/tag: add maildir sync tests 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. 2023-09-30 08:40:50 -03:00			`time_run 'tag * +maildir_flag F' "notmuch tag +flagged '*'"`
			`time_run 'tag * -maildir_flag F' "notmuch tag -flagged '*'"`
			`time_run 'tag * +maildir_flag P' "notmuch tag +passed '*'"`
			`time_run 'tag * -maildir_flag P' "notmuch tag -passed '*'"`
			`time_run 'tag * +maildir_flag D' "notmuch tag +draft '*'"`
			`time_run 'tag * -maildir_flag D' "notmuch tag -draft '*'"`
			`time_run 'tag * +maildir_flag S' "notmuch tag -unread '*'"`
			`time_run 'tag * -maildir_flag S' "notmuch tag +unread '*'"`

perf-test: split basic into 00-new, 01-dump-restore, and 02-tag We use the new "time_start" function to restore the database from cache if possible. 2012-12-05 21:34:30 -04:00			`time_done`