This section can be omitted in standalone mode.
Agents section forms either a list or map with arbitrary agent names and either an inline or properties-style definition:
someAgent: "inline definition"
The definition is passed to an instance of
i.h.api.deployment.Deployer which will interpret the definition. Deployer implementation is registred using the
java.util.ServiceLoader and selected through the
io.hyperfoil.deployer system property. The default implementation is
|Number of threads used by the agent (overrides
threads in benchmark root).
|Custom options passed to the JVM (system properties, JVM options…)
The user account running Hyperfoil Controller must have a public-key authorization set up on agents’ hosts using key
$HOME/.ssh/id_rsa. It also has to be able to copy files into the
dir directory using SCP - all the required JARs will be copied there and you will find the logs there as well.
ssh deployer accepts either the
[user@]host[:port] inline syntax or these properties:
|This property is mandatory.
|Directory set by system property
|Working directory for the agent. This directory can be shared by multiple agents running on the same physical machine.
|If set the CPUs where the agent can run is limited using
taskset -c <cpu>. Example:
See an example of ssh deployment configuration:
To activate the kubernetes deployer you should set
-Dio.hyperfoil.deployer=k8s; the recommended installation does that automatically.
The agents are configured the same way as with SSH deployment, only the properties differ. Full reference is provided below.
|Configures the labels for the
nodeSelector. If the value does not contain equals sign (
=) or comma (
,) this sets the desired value of label
kubernetes.io/hostname. You can also set multiple custom labels separated by commas, e.g.
|By default the controller stops all agents immediatelly after the run terminates. In case of errors this is not too convenient as you might want to perform further analysis. To prevent automatic agent shutdown set this to false.
|Name of config map (e.g.
my-config-map) or config map and its entry (e.g.
my-config-map/log4j2.xml) that contains the Log4j2 configuration file. Default entry from the config map is
log4j2.xml. Hyperfoil will mount this configmap as a volume to this agent.
|Different version of Hyperfoil in the agents
|Image pull policy for agents
|Automatically watch agents’ logs and store them in the run directory.