Measure Windows on Arm resource usage with FFmpeg and PowerShell
Introduction
Set up FFmpeg and encode a test video
Track system resource usage on Windows on Arm with PowerShell
Measure power usage on Windows on Arm with PowerShell
Next Steps
Measure Windows on Arm resource usage with FFmpeg and PowerShell
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Set the
exePath parameter to the specific FFmpeg or FFplay binary that you want to run. Use the Arm64-native build for Arm execution, or point to an x86_64 build to run under Windows instruction emulation.While the decode task runs, the script writes samples to a CSV file. Check that the CSV file appears and grows over time, and that it contains headers and rows with CPU and memory values.
Verify the input and output file paths and confirm the arguments match the media you’re using. Ensure
exePath points to a valid FFmpeg or FFplay binary and review the console output for specific errors.The output file name and path are defined in each script. Open the script to confirm or change the location. Expect timestamped rows with the recorded metrics, such as CPU and memory for resource sampling, or battery-related fields for power sampling.
Use the same media file, the same command arguments, and the same sampling settings for both runs. Point
exePath to each build in turn and compare the resulting CSV files.