All Classes and Interfaces
Class
Description
One route from an exchange into a queue.
What a particular broker will actually give you.
java -jar acemq-workload.jar -f workload.yamlStarts the standing loads, or adopts ones already running, reports on them, and stops them.
A load being watched: its pid, and whether this call started it.
A load could not be started or stopped.
What a load is doing right now.
The workload file is wrong.
The consumers on one queue.
How the load is consumed.
The leak drill: standing loads in every language, and every connection torn out from under all
of them, over and over, while the run watches what each process is holding rather than what it
is publishing.
The repeated recovery fault, and the connection count that proves it did something.
What the run is doing, for a console or a terminal.
What the run found and where it wrote it.
java -jar acemq-workload.jar endurance [options]: the soak.What an endurance run is asked to do: the soak's numbers, the clients to watch and how each one
is started, the allowances a leak has to cross, and the upstream defects allowed within a
measured ceiling.
Growth a client is allowed before it is a leak.
A breach a library is known to have for a reason nothing in the workspace can fix, with a
ceiling of its own:
base * factor + perRecovery * recoveries + plus.How one standing load is started.
An exchange in a scenario.
What a scenario is asked to prove.
One thing a rule noticed, with the measurement that made it say so.
Records latencies, from many threads, without distorting them.
Latency percentiles from one run.
java -jar acemq-workload.jar loads up|down|status: the standing loads a chaos drill
watches, started, stopped and reported on through the same ClientLauncher the soak
uses.Something in a scenario that can be switched off without being removed.
What the run has to achieve to count as a pass.
The bytes a workload publishes, and the header this library needs inside them.
What a process is holding, read from outside it.
Linux:
/proc/<pid>/status for VmRSS and Threads, and the entries of
/proc/<pid>/fd for descriptors.macOS and other Unixes:
ps -o rss=, lsof -p and ps -M, counted
exactly as scripts/soak.sh counted them so a report from either compares with the
other: every line lsof prints, header included, and every thread line ps prints after its
header.One source of load, aimed at one exchange.
How the load is offered.
A queue in a scenario, its bindings, and the consumers on it.
The kinds of queue a scenario can ask for.
Steps the offered rate up until something gives, to find the highest rate a broker sustains.
What a
Ramp found: every step, the highest rate that met every rule and objective, and
what stopped it.One step.
One client, read once from outside: one line of the readings TSV.
Renders runs as JSON, Markdown or HTML.
Something checked against a finished run.
The rules that run on every workload, whether or not anybody asked for them.
A run in progress.
Watches a run as it happens.
One reading taken while a workload is running.
What a run is doing when a reading is taken.
A whole topology under load, rather than one queue.
A scenario as a file.
An exchange.
What a node is asked to prove, in a file.
A queue, its bindings and its consumers.
How to reach a broker over TLS.
A scenario in progress.
Watches a scenario as it runs.
Reads a scenario file from disk.
A scenario file that cannot be read, with what is wrong with it.
What a scenario did, node by node.
What one producer managed.
What one queue saw.
A scenario's report as a file.
Starts scenarios.
One reading of a whole scenario, node by node.
What one producer is doing.
What one queue is doing.
How much a
Finding matters, worst first.A rule written as a threshold on one number in the report — the shape of the admin library's
alerts, so a rule reads the same whether it watches a broker or judges a run.
What the workload publishes to and consumes from.
The soak's verdict, from its readings: medians of the baseline and final readings per client,
against the allowances, with known upstream breaches classified rather than failed.
One client's before and after.
A load test, described.
Builds a
Workload.Reads a workload, or a suite of them, from YAML or JSON.
What one run measured, and what the rules made of it.
Finds the comments in a YAML document, so that substitution can leave them alone.