<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmarking :: FirmwareCI</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/index.html</link><description>System performance benchmarking and power state testing commands.
AMD S2Idle S0ix-Selftest Fio Iperf3 Stress-NG Expect Comparator Syntax The fio, iperf3, and stress-ng steps assert measured metrics against comparator strings. Empty (or omitted) means “no assertion”.
Form Meaning &lt;N Measured value must be ≤ N &gt;N Measured value must be ≥ N =N Measured value must equal N N-M Measured value must be within [N, M] All comparisons are integer. Float metrics (bandwidth, latency, ops/sec) are truncated before comparison.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://docs.firmware-ci.com/references/2_commands/benchmarking/index.xml" rel="self" type="application/rss+xml"/><item><title>AMD S2Idle</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/amd-s2idle/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/benchmarking/amd-s2idle/index.html</guid><description>Test AMD S2Idle (suspend-to-idle) functionality using the AMD debug tools. This command runs comprehensive suspend/resume cycle testing with detailed validation and reporting.
The DUT needs amd-s2idle on PATH. The step runs it without sudo, so connect as root. The step also runs ethtool to enable Wake-on-LAN and only logs a warning when this fails. To get both tools in an image built on the FirmwareCI base image, set firmwareci.amdDebug.enable = true.
Attribute Type Required Default Description cmd const Yes amd-s2idle Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject Yes Additional transport options options OptionsObject No Additional command options parameters AMDS2IdleOptions No Options passed into the amd-s2idle tool AMD S2Idle Options Attribute Type Required Default Description count integer No 10 Number of suspend/resume cycles to run duration integer No 10 Duration of each suspend cycle in seconds wait integer No 4 Time to wait before starting each cycle in seconds format string No stdout Format of the report to produce. Options: html, txt, md, stdout report_file string No File path to write the report to (only applicable if format is html, txt, or md) force boolean No false Run test cycle even if the system fails prerequisite checks random boolean No false Run sleep cycles with random durations and waits (using duration and wait as upper bounds) logind boolean No false Use systemd-logind to suspend the system tool_debug boolean No false Enable debug logging for the tool bios_debug boolean No false Enable BIOS/firmware debug logging AMD S2Idle Examples Basic Usage cmd: amd-s2idle name: Run AMD S2Idle test with defaults transport: proto: ssh options: host: "[[attributes.Host]]" user: root Custom Parameters cmd: amd-s2idle name: Run extended AMD S2Idle test transport: proto: ssh options: host: "[[attributes.Host]]" user: root options: timeout: 30m parameters: count: 20 duration: 15 wait: 5 format: html report_file: /tmp/s2idle-report.html With Debug Logging cmd: amd-s2idle name: Run AMD S2Idle test with debug logging transport: proto: ssh options: host: "[[attributes.Host]]" user: root parameters: count: 5 duration: 10 tool_debug: true bios_debug: true</description></item><item><title>S0ix-Selftest</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/s0ix-selftest/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/benchmarking/s0ix-selftest/index.html</guid><description>Test S0ix (suspend-to-idle) power state functionality. The DUT needs s0ix-selftest-tool on PATH and sudo.
Attribute Type Required Default Description cmd const Yes s0ix-selftest Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject Yes Additional transport options options OptionsObject No Additional command options S0ix-Selftest Example cmd: s0ix-selftest name: Run s0ix selftest transport: *transport</description></item><item><title>Fio</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/fio/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/benchmarking/fio/index.html</guid><description>Run fio on the DUT and assert against parsed metrics. The fio binary must be installed on the DUT. The FirmwareCI base image does not include it.
Attribute Type Required Default Description cmd const Yes fio Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject Yes Additional transport options options OptionsObject No Additional command options (default timeout 2m) parameters FioOptions Yes Options passed into the fio cmd Fio Options Attribute Type Required Default Description args []string No randread 4k 1G 30s job Raw arguments passed to fio. If omitted, runs a default randread workload against /tmp/contest-fio-&lt;nano&gt;.dat. --output-format=json auto-added. expect FioExpect No Per-metric assertions. See Expect Comparator Syntax. Fio Expect Options Assertions run against the first job in fio’s JSON output.</description></item><item><title>Iperf3</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/iperf3/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/benchmarking/iperf3/index.html</guid><description>Run iperf3 in client mode against a remote server and assert against the bandwidth summary. The iperf3 binary must be installed on the DUT, and an iperf3 -s peer must be reachable. The FirmwareCI base image does not include it.
Attribute Type Required Default Description cmd const Yes iperf3 Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject Yes Additional transport options options OptionsObject No Additional command options (default timeout 2m) parameters Iperf3Options Yes Options passed into the iperf3 cmd Iperf3 Options Attribute Type Required Default Description args []string Yes Raw arguments passed to iperf3. Must include -c &lt;host&gt; (client mode); server mode is out of scope. -J auto-added. expect Iperf3Expect No Per-metric assertions. See Expect Comparator Syntax. Iperf3 Expect Options Assertions run against end.sum_received (TCP) or end.sum (UDP).</description></item><item><title>Stress-NG</title><link>https://docs.firmware-ci.com/references/2_commands/benchmarking/stress-ng/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/benchmarking/stress-ng/index.html</guid><description>Run stress-ng on the DUT and assert against the --metrics-brief rows aggregated across all stressors. The stress-ng binary must be installed on the DUT.
Attribute Type Required Default Description cmd const Yes stress-ng Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject Yes Additional transport options options OptionsObject No Additional command options (default timeout 2m) parameters StressNGOptions Yes Options passed into the stress-ng cmd Stress-NG Options Attribute Type Required Default Description args []string No --cpu 0 --timeout 30s --metrics-brief Raw arguments passed to stress-ng. If supplied, must include --metrics-brief so per-stressor metric rows are emitted. expect StressNGExpect No Per-metric assertions. See Expect Comparator Syntax. Stress-NG Expect Options Values are summed across every stressor row in the output.</description></item></channel></rss>