The bench script invoked by cabal bench or stack bench now links the benchmarked code directly, avoiding any dependence on the shell and $PATH. Also, it reports the journal parse time and the various reports on the parsed data separately, and runs quicker. You can get more accurate benchmark times by running with --criterion. This will usually give much the same numbers and takes much longer. Benchmarking via simplebench is still available, by running with --simplebench. In this mode it benchmarks whatever commands are configured in bench/default.bench. A disadvantage is that it uses the first "hledger" executable in $PATH, so check which one it reports.
		
			
				
	
	
		
			9 lines
		
	
	
		
			116 B
		
	
	
	
		
			YAML
		
	
	
	
	
	
			
		
		
	
	
			9 lines
		
	
	
		
			116 B
		
	
	
	
		
			YAML
		
	
	
	
	
	
| packages:
 | |
| - hledger-lib
 | |
| - hledger
 | |
| - hledger-web
 | |
| flags: {}
 | |
| resolver: nightly-2015-06-17
 | |
| extra-deps:
 | |
| - timeit-1.0.0.0
 |