forked from cloud-bulldozer/benchmark-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ripsaw_v1alpha1_hammerdb_cr.yaml
37 lines (35 loc) · 1.38 KB
/
ripsaw_v1alpha1_hammerdb_cr.yaml
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
apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
name: hammerdb-benchmark-example
namespace: my-ripsaw
spec:
# where elastic search is running
elasticsearch:
url: http://my.elasticsearch.server:80
verify_cert: false
parallel: false
# clustername: myk8scluster
# test_user: ripsaw
workload:
name: hammerdb
args:
## 'initialize' enables the schema creation in the db if it's not done already
## 'benchmark' enables the actual benchmarking using the parameters further down below
db_init: true
db_benchmark: true
## Standard options used for all operations, initialization and benchmark
db_server: "mssql-deployment.sql-server"
db_port: "1443"
db_user: "SA"
db_pass: "s3curePasswordString"
db_warehouses: 1
db_num_workers: 1
db_tcp: "true"
## Workload specific settings
## runtime and transactions are mutually exclusive, transactions will override runtime
transactions: 100000
runtime: 30 # corresponds to runtimer in the tcl script (in minutes)
rampup: 1 # corresponds to mssqls_rampup in the tcl script (minutes)
samples: 3 # needs to be implemented
#clients: 4 # corresponds to virtual users (vu) in the tcl script, this should be the maximum number of clients which we approach logarithmically (sp?)