-
Notifications
You must be signed in to change notification settings - Fork 1
/
px-bench-env.yml
46 lines (42 loc) · 2.31 KB
/
px-bench-env.yml
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
apiVersion: v1
kind: ConfigMap
metadata:
name: env
namespace: px-bench
data:
#node_selector: "kubernetes.io/hostname=node-1-1" # uncomment to pin fio to node(s)
# Options that control the underlying fio benchmark utility. These equate to the same-named option in fio
file_size: "10GiB" # size of region of IO testing, will also be the size of the file
pvc_size: "50Gi" # If the storageclass is backed by a larger disk from infrastructure,
# such as a Portworx pool, then pvc_size should be the same size as
# the backing storage if it's desired to be testing the same
# size and performance storage (See TheoryOfOps.md)
runtime: "20" # runtime in seconds. Start low the first time to ensure everything
# is working as planned. Then increase to desired runtime.
iodepth: "128"
rwmixread: "60" # only used for readwrite and randrw workloads
rwmixwrite: "40" # should be 100 - rwmixread
ramp_time: "5" # ramp time per test. As with runtime, keep low for quick tests
# and then increase to desired ramp_time for later tests
# Less commonly changed fio options
ioengine: "libaio"
direct: "1"
fsync_on_close: "1"
numjobs: "1"
group_reporting: "1"
######
# px-bench specific options. These are not fio options
mixed_workloads: "rw readwrite randrw" # rw is a synonym for readwrite
######
# Iteration Control: Each variable will be looped over to create the jobs to be run.
# Do not change the variable name. The variable must consist of one or more space
# delimited strings that are legal values for fio to use in a job file.
#
# For now, the only supported variables here are blocksize and randwrite
#
# Example: If you have 2 blocksize values, and 3 randwrite values, this will result in 6 jobfiles.
blocksize_list: "4k 16k 256k" # We have not tested fio's support for different values for read and write ("bs=8k,32k")
readwrite_list: "read write readwrite" # valid values are read, write, randread, readwrite (or rw), randrw.
storageclass_list: "storageclass-1 storageclass-2" # Existing storageclasses for use by the benchmarks
warmup_blocksize: 256k
warmup_loops: "1"