<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CPU Operations :: FirmwareCI</title><link>https://docs.firmware-ci.com/references/2_commands/cpu-operations/index.html</link><description>CPU performance monitoring, profiling, and testing commands.
CPULoad CPUSet CPUStats SysBench</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://docs.firmware-ci.com/references/2_commands/cpu-operations/index.xml" rel="self" type="application/rss+xml"/><item><title>CPULoad</title><link>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpuload/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpuload/index.html</guid><description>Run a CPU-Load test on the DUT. The DUT needs sudo and stress-ng. It also needs turbostat when expect is set, and taskset when cpus is set without args.
Attribute Type Required Default Description cmd const Yes cpuload Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject No Additional transport options options OptionsObject No Additional command options parameters CPULoadOptions No parameters cpuload Options CPULoad Options Attribute Type Required Default Description args []string Yes Array of strings with arguments passed into the cpuload tool. cpus []integer Yes Array of CPUs that should be put under load. duration string Yes Duration of the load. Format: ^((\\d+h)?(\\d+m)?(\\d+s)?)?$ expect CPUExpectOptions Yes Expected values CPULoad Example cmd: cpuload name: Check cpu frequencies with load transport: *transport options: timeout: 2m parameters: duration: 1m expect: individual: - cpus: [0, 1, 2, 3, 4, 5, 6, 7] option: AverageFrequency value: "&gt;1500" - cpus: [8, 9, 10, 11, 12, 13, 14, 15] option: AverageFrequency value: "&gt;1200"</description></item><item><title>CPUSet</title><link>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpuset/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpuset/index.html</guid><description>Set cpu profiles on the DUT. The DUT needs sudo.
Attribute Type Required Default Description cmd const Yes cpuset Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject No Additional transport options options OptionsObject No Additional command options parameters CPUSetOptions Yes Options passed into the cpuset cmd CPUSet Options Attribute Type Required Default Description command string Yes Command to run. Available options: core, or profile. cores []integer No Array of Cores where the command should be applied to. If not set apply to all arg string Yes Value of the command option CPUSet Example cmd: cpuset name: Set ACPI Platform Profile to low-power transport: *transport parameters: command: profile arg: low-power</description></item><item><title>CPUStats</title><link>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpustats/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/cpu-operations/cpustats/index.html</guid><description>Monitor and validate CPU statistics on the DUT. The DUT needs sudo and turbostat.
Attribute Type Required Default Description cmd const Yes cpustats Command Name name string Yes Name to uniquely identify the teststep. This name will show up in reports, logs and the WebUI transport TransportObject No Additional transport options options OptionsObject No Additional command options parameters CPUStatsOptions Yes parameters cpustats Options CPUStats Options Attribute Type Required Default Description interval string No Testing interval time expect CPUExpectOptions Yes Expected values CPU Expect Options Attribute Type Required Default Description general []GeneralObject No expect General Expected Values individual []IndividualObject No Individual CPU Expected Values General Object Values that describe the machine as a whole.</description></item><item><title>SysBench</title><link>https://docs.firmware-ci.com/references/2_commands/cpu-operations/sysbench/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.firmware-ci.com/references/2_commands/cpu-operations/sysbench/index.html</guid><description>Run SysBench on the DUT. The DUT needs sysbench.
Attribute Type Required Default Description cmd const Yes sysbench 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 SysBenchOptions Yes Options passed into the sysbench cmd SysBench Options Attribute Type Required Default Description args []string No Arguments to pass to sysbench. expect []ExpectOptions Yes Expectations to check against the output of sysbench. SysBench Expect Options Attribute Type Required Default Description option string Yes Option to check value string Yes Expected value SysBench Example cmd: sysbench name: Benchmark transport: *transport parameters: args: [cpu, --cpu-max-prime=20000, --threads=18, --time=60, run] expect: - option: EventsPerSecond value: &lt;4500</description></item></channel></rss>