notmuch/performance-test/.gitignore

tmp.*/
log.*/
corpus/
notmuch.cache.*/
test: initial performance testing infrastructure 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 2012-11-17 17:28:15 +01:00			`tmp.*/`
perf-test: initial version of memory test infrastructure. The idea is run some code under valgrind --leak-check=full and report a summary, leaving the user to peruse the log file if they want. We go to some lengths to preserve the log files from accidental overwriting; the full corpus takes about 3 hours to run under valgrind on my machine. The naming of the log directories may be slightly controversial; in the unlikely event of two runs in less than a second, the log will be overwritten. A previous version with mktemp+timestamp was dismissed as overkill; just mktemp alone does not sort nicely. One new test is included, to check notmuch new for memory leaks. 2012-12-16 13:33:17 +01:00			`log.*/`
perf-test: cache unpacked corpus Unpacking is not really the expensive step (compared to the initial notmuch new), but this is a pre-requisite to caching the database. 2012-12-03 13:13:31 +01:00			`corpus/`
perf-test: add caching of xapian database The caching and uncaching seem to be necessarily manual, as timing the initial notmuch new is one of our goals with this suite. 2012-12-03 13:48:53 +01:00			`notmuch.cache.*/`