mirror of
https://github.com/nosqlbench/nosqlbench.git
synced 2025-02-25 18:55:28 -06:00
improve examples, illustrate conventions
This commit is contained in:
@@ -1,39 +0,0 @@
|
||||
# You can run this file with this command line to see the values printed to stdout:
|
||||
# ./ebdse run driver=stdout yaml=bindings/double.yaml cycles=10
|
||||
|
||||
# This file demonstrates different types of timestamp recipes
|
||||
# that you can use with virtdata. (The bindings used in ebdse)
|
||||
|
||||
# If you want to control the output, uncomment and edit the statement template below
|
||||
# and modify the named anchors to suit your output requirements.
|
||||
|
||||
#statements:
|
||||
# example1: "{fullname}\n"
|
||||
|
||||
bindings:
|
||||
|
||||
# All uncommented lines under this are indented, so they become named bindings below
|
||||
# the entry above
|
||||
|
||||
# Normally, the value that you get with a cycle starts at 0.
|
||||
|
||||
cycleNum: Identity();
|
||||
|
||||
# here we convert the cycle number to a double by casting.
|
||||
id: Identity(); ToDouble()
|
||||
|
||||
## Sensor value
|
||||
sensor_value: Normal(0.0,5.0); Add(100.0) -> double
|
||||
|
||||
# Example output:
|
||||
|
||||
# sensor_value : 97.65195455640468
|
||||
# sensor_value : 102.36957817450308
|
||||
# sensor_value : 106.1618147543308
|
||||
# sensor_value : 105.69436460281086
|
||||
# sensor_value : 95.76439295584129
|
||||
# sensor_value : 99.79975449386073
|
||||
# sensor_value : 102.3330464938251
|
||||
# sensor_value : 100.58103001489948
|
||||
# sensor_value : 99.15058382227814
|
||||
# sensor_value : 97.17512591189272
|
||||
@@ -1,36 +0,0 @@
|
||||
# You can run this file with this command line to see the values printed to stdout:
|
||||
# ./ebdse run driver=stdout yaml=bindings/timestamp.yaml cycles=10
|
||||
|
||||
# This file demonstrates different types of timestamp recipes
|
||||
# that you can use with virtdata. (The bindings used in ebdse)
|
||||
|
||||
# If you want to control the output, uncomment and edit the statement template below
|
||||
# and modify the named anchors to suit your output requirements.
|
||||
|
||||
#statements:
|
||||
# example1: "{epochMillis}\n"
|
||||
|
||||
bindings:
|
||||
|
||||
# All uncommented lines under this are indented, so they become named bindings below
|
||||
# the entry above
|
||||
|
||||
# Normally, the value that you get with a cycle starts at 0.
|
||||
|
||||
cycleNum: Identity();
|
||||
# All uncommented lines under this are indented, so they become named bindings below
|
||||
# the entry above
|
||||
|
||||
# You can offset the start of your millis to some formatted date.
|
||||
# Notice, that in this case, the result is still in millis since the epoch
|
||||
|
||||
randomMillisStartingFeb2018: StartingEpochMillis('2018-02-01 05:00:00');
|
||||
|
||||
# You can randomly offset the value by some amount as shown below.
|
||||
# In this case, the AddHashRange(...) function is internally hashing
|
||||
# the input value and down-sampling it to the range specified, and then
|
||||
# adding the resulting value to the input. The range is selected as
|
||||
# 0,2419200000 because that is how many milliseconds there are in February.
|
||||
|
||||
randomMillisWithinFeb2018: AddHashRange(0,2419200000L); StartingEpochMillis('2018-02-01 05:00:00');
|
||||
|
||||
Reference in New Issue
Block a user