InfluxDB is a purpose-built time-series database written in Go from
InfluxData. This supplemental guide explains how
the data generated for TSBS is stored, additional flags available when
using the data importer (tsbs_load_influx), and additional flags
available for the query runner (tsbs_run_queries_influx). This
should be read after the main README.
If on a new setup run the following command:
influx setupIf you need to create a new bucket adjust the bucket name (-n) and the org name (-o) accordingly:
influx bucket create -n bucket-perf -o org -r 0Create a DBRP mapping with the InfluxDB 1.x compatibility API (official docs).
Adjust bucket name and db accordingly:
influx v1 dbrp create --db benchmark --rp 0 --bucket-id `influx bucket ls --name bucket-perf | awk -v i=2 -v j=1 'FNR == i {print $j}'` --defaultRetrieve the auth token as follows:
influx auth listData generated by tsbs_generate_data for InfluxDB is serialized in a
"pseudo-CSV" format. Each reading is composed of a single line where
the name of the table is the first item, a comma, followed by several
comma-separated items of tags in the format of <label>=<value>, a space,
several comma-separated items of fields in the format of <label>=<value>,
a space, and finally the timestamp for the reading.
An example for the cpu-only use case:
cpu,hostname=host_0,region=eu-central-1,datacenter=eu-central-1b,rack=21,os=Ubuntu15.10,arch=x86,team=SF,service=6,service_version=0,service_environment=test usage_user=58.1317132304976170,usage_system=2.6224297271376256,usage_idle=24.9969495069947882,usage_nice=61.5854484633778867,usage_iowait=22.9481393231639395,usage_irq=63.6499207106198313,usage_softirq=6.4098777048301052,usage_steal=44.8799140503027445,usage_guest=80.5028770761136201,usage_guest_nice=38.2431182911542820 1451606400000000000
Consistency level for writes to the database. Options are all, any, one,
or quorum. Only applies for the clustered version.
Level of replication for each write, i.e., number of nodes to store the data on. Only applies for the clustered version.
Comma-separated list of URLs to connect to for inserting data. Workers will be distributed in a round robin fashion across the URLs.
The amount of time per retry attempt when the server says it is too busy. A
longer backoff will potentially reduce write performance by waiting too long to
retry, leaving the system idle. It is expressed as a Golang time.Duration
string, meaning a number followed by a unit abbreviation (s = seconds,
m = minutes, h = hours), e.g., the default 1s is one second.
Whether to encode writes to the server with gzip. For best performance, encoding with gzip is the best choice, but if the server does not support or has gzip disabled, this flag should be set to false.
Use the Authorization header with the Token scheme to provide your token to InfluxDB. If empty will not send the Authorization header.
Number of series to return per response per query. If the query would generate a response that is very large, it could cause the server to crash with out-of-memory problems. This flag will chunk the response into multiple smaller responses to prevent the server from crashing. The default of 0 will return everything in a single response.
Comma-separated list of URLs to connect to for querying. Workers will be distributed in a round robin fashion across the URLs.
Use the Authorization header with the Token scheme to provide your token to InfluxDB. If empty will not send the Authorization header.