Lines Matching +full:power +full:- +full:sample +full:- +full:average
1 This is cpufreq-bench, a microbenchmark for the cpufreq framework.
7 - Identify worst case performance loss when doing dynamic frequency
9 - Identify average reaction time of a governor to CPU load changes
10 - (Stress) Testing whether a cpufreq low level driver or governor works
12 - Identify cpufreq related performance regressions between kernels
13 - Possibly Real time priority testing? -> what happens if there are
15 - ...
18 - Power saving related regressions (In fact as better the performance
19 throughput is, the worse the power savings will be, but the first should
21 - Real world (workloads)
27 cpufreq-bench helps to test the condition of a given cpufreq governor.
80 trigger of the cpufreq-bench, you will see no performance loss (compare with
81 below possible ondemand sample kick ins (1)):
85 switching up (compare with below possible ondemand sample kick ins (2))::
87 50 50 50 50ms ->time
88 load -----| |-----| |-----| |-----|
90 sleep |-----| |-----| |-----| |----
91 |-----|-----|-----|-----|-----|-----|-----|---- ondemand sampling (1)
93 |-----|-----|-----|-----|-----|-----|-----|-- ondemand sampling (2)
97 governor in average behaves as expected.
107 cpufreq-bench Command Usage
109 -l, --load=<long int> initial load time in us
110 -s, --sleep=<long int> initial sleep time in us
111 -x, --load-step=<long int> time to be added to load time, in us
112 -y, --sleep-step=<long int> time to be added to sleep time, in us
113 -c, --cpu=<unsigned int> CPU Number to use, starting at 0
114 -p, --prio=<priority> scheduler priority, HIGH, LOW or DEFAULT
115 -g, --governor=<governor> cpufreq governor to test
116 -n, --cycles=<int> load/sleep cycles to get an average value to compare
117 -r, --rounds<int> load/sleep rounds
118 -f, --file=<configfile> config file to use
119 -o, --output=<dir> output dir, must exist
120 -v, --verbose verbose output on/off