-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathrebench.conf
66 lines (61 loc) · 1.72 KB
/
rebench.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
# -*- mode: yaml -*-
# Config file for ReBench
default_experiment: benchmarks
default_data_file: 'rebench.data'
reporting:
# Benchmark results will be reported to ReBenchDB
rebenchdb:
# this url needs to point to the API endpoint
db_url: https://rebench.stefan-marr.de/rebenchdb
repo_url: https://github.com/smarr/ReBenchDB
record_all: true # make sure everything is recorded
project_name: ReBenchDB
runs:
max_invocation_time: 6000
min_iteration_time: 1
benchmark_suites:
normal:
gauge_adapter: RebenchLog
command: "harness.js %(benchmark)s %(iterations)s 1 %(input)s "
location: dist/src/benchmarks
iterations: 10
invocations: 1
input_sizes:
- small
- medium
- large
benchmarks:
- store-results
- fetch-results
- compute-timeline
- render-report
full:
gauge_adapter: RebenchLog
command: "harness.js %(benchmark)s %(iterations)s 1 %(input)s "
location: dist/src/benchmarks
iterations: 1
invocations: 1
input_sizes:
- full
benchmarks:
- store-results
- compute-timeline
- render-report
executors:
benchmarks:
executable: /usr/local/bin/node
env:
RDB_USER: docker
RDB_PASS: docker
RDB_HOST: localhost
RDB_DB: rebenchdb
NODE_ENV: test
# define the benchmarks to be executed for a re-executable benchmark run
experiments:
benchmarks:
description: All benchmarks
suites:
- normal
- full
executions:
- benchmarks