Hi Michael, sorry for getting back to this after such a delay.

Originally Posted by
Michael
- it should be shown in the documentation.
Sorry, can't find it anywhere. The old-docs/result-parser.xml refers to a "phodevi name" of a sensor, but I can't figure out where I should get these names. The PTS' system-sensors command only outputs human-friendly names:
Code:
$ phoronix-test-suite system-sensors
Phoronix Test Suite v4.4.0m3
Supported Sensors
CPU Frequency: 2.30 Megahertz
CPU Usage: 16.70 Percent
...

Originally Posted by
Michael
- the delimiter is a comma, you can also use MONITOR=all or say MONITOR=cpu.all
Ahh, so if I want to monitor, say CPU usage and memory usage, I launch:
MONITOR=cpu.usage,memory.usage phoronix-test-suite benchmark...

Originally Posted by
Michael
- Can you elaborate? You can already use MONITOR= with any test profile.
I mean that the user has to remember to launch PTS with these parameters. Would it be possible to define some sort of "default" list of sensors inside test-definition.xml, which would be monitored (unless overridden by manually specifying the MONITOR variable), so that the burden is taken away from the user?
Looking at the existing PTS test profiles, I can only see profiles with a single sensor in results-definition. My goal is to define a result based on some command output or only one sensor too, but monitor and save a chart for multiple sensors from a single run.