Directories
¶
| Path | Synopsis |
|---|---|
|
Command bench measures Dicer on the host it runs on, for the numbers the documentation publishes and to see what a change does to them.
|
Command bench measures Dicer on the host it runs on, for the numbers the documentation publishes and to see what a change does to them. |
|
harness
Package harness is what every scenario of the benchmarks shares: the daemon's client, the instances, networks and snapshots a scenario makes, which it always removes, reading the host's memory, CPU and disk, and recording what was measured.
|
Package harness is what every scenario of the benchmarks shares: the daemon's client, the instances, networks and snapshots a scenario makes, which it always removes, reading the host's memory, CPU and disk, and recording what was measured. |
|
probe
Package probe is work whose speed says what a machine can do: hashing and compressing for its CPU, and reading and writing a file for its disk.
|
Package probe is work whose speed says what a machine can do: hashing and compressing for its CPU, and reading and writing a file for its disk. |
|
result
Package result is what a run of the benchmarks found, as the JSON it is kept in, and the tables and comparisons made from it.
|
Package result is what a run of the benchmarks found, as the JSON it is kept in, and the tables and comparisons made from it. |
|
scenario
Package scenario is the benchmarks' scenarios: each one thing to measure, such as how fast an instance boots or how many fit on the host, run with parameters a suite or the command line gives it.
|
Package scenario is the benchmarks' scenarios: each one thing to measure, such as how fast an instance boots or how many fit on the host, run with parameters a suite or the command line gives it. |
|
suite
Package suite reads suites: YAML files that say which scenarios a run of the benchmarks makes, and with which parameters.
|
Package suite reads suites: YAML files that say which scenarios a run of the benchmarks makes, and with which parameters. |
|
workload
Package workload is what the benchmarks' guests do: the programs they run, how to tell they are ready, and the requests sent to them.
|
Package workload is what the benchmarks' guests do: the programs they run, how to tell they are ready, and the requests sent to them. |
|
Command docgen generates the documentation site's reference pages from the code: the command line from the commands, the configuration and the compose file from the doc comments on the types they are read into, the Go client from the doc comments of the package at the module's root, and the metrics from those the daemon registers.
|
Command docgen generates the documentation site's reference pages from the code: the command line from the commands, the configuration and the compose file from the doc comments on the types they are read into, the Go client from the doc comments of the package at the module's root, and the metrics from those the daemon registers. |
Click to show internal directories.
Click to hide internal directories.