notmuch/performance-test/T01-dump-restore.sh

#!/usr/bin/env bash

test_description='dump and restore'

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

time_start

time_run 'load nmbug tags' 'notmuch restore --accumulate < corpus.tags/nmbug.sup-dump'
time_run 'dump *' 'notmuch dump > tags.out'
time_run 'restore *' 'notmuch restore < tags.out'

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='dump and restore'`

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`

perf-test: use nmbug tags in dump-restore tests This makes the tag set a bit less trivial. Note that if you use the small corpus, this is not so interesting (and is also a bit noisy) since the messages will not be found. In the future this could be checked for. Conflicts: performance-test/01-dump-restore 2012-12-05 22:12:16 -04:00			`time_run 'load nmbug tags' 'notmuch restore --accumulate < corpus.tags/nmbug.sup-dump'`
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_run 'dump *' 'notmuch dump > tags.out'`
			`time_run 'restore *' 'notmuch restore < tags.out'`

			`time_done`