notmuch/performance-test/M04-reply.sh

#!/usr/bin/env bash

test_description='search'

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

memory_start

for id in $(notmuch search --output=messages '*' | shuf -n 5); do
    memory_run "reply $id" "notmuch reply \"$id\" 1>/dev/null"
    memory_run "reply --format=json $id" "notmuch reply --format=json \"$id\" 1>/dev/null"
    memory_run "reply --format=sexp $id" "notmuch reply --format=sexp \"$id\" 1>/dev/null"
done

memory_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 20:32:50 +02:00			`#!/usr/bin/env bash`
perf-test: add memory test for reply Looking at the code for notmuch-reply, there seems to be several gmime related memory leaks. This test is supposed to help eliminate those. 2017-05-27 18:51:14 +02:00
			`test_description='search'`

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 22:38:20 +02:00			`. $(dirname "$0")/perf-test-lib.sh \|\| exit 1`
perf-test: add memory test for reply Looking at the code for notmuch-reply, there seems to be several gmime related memory leaks. This test is supposed to help eliminate those. 2017-05-27 18:51:14 +02:00
			`memory_start`

			`for id in $(notmuch search --output=messages '*' \| shuf -n 5); do`
			`memory_run "reply $id" "notmuch reply \"$id\" 1>/dev/null"`
			`memory_run "reply --format=json $id" "notmuch reply --format=json \"$id\" 1>/dev/null"`
			`memory_run "reply --format=sexp $id" "notmuch reply --format=sexp \"$id\" 1>/dev/null"`
			`done`

			`memory_done`