On 08/21/2015 07:44 AM, Leo Yan wrote:
Hi Dietmar,
On Fri, Aug 21, 2015 at 07:09:09AM -0700, Dietmar Eggemann wrote:
On 08/21/2015 12:57 AM, Leo Yan wrote:
[...]
BTW, i saw Morten's patch series have some performance comaparsion for sysbench and rt-app's cases, like below table's colume "prf"; so could you help explain how to get these performance result?
Energy Mainline (ndm) noEAS (ndm) EAS (ndm) EAS (sched) nrg prf nrg prf nrg prf nrg prf sysbench 100 100 107 105 108 105 107 105
Run 'sysbench --test=cpu --num-threads=1 --max-time=30 run'
and take the number of events as your performance score:
# sysbench --test=cpu --num-threads=1 --max-time=30 run sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options: Number of threads: 1
...
Test execution summary: total time: 30.0069s total number of events: 986
...
The numbers are normalized against mainline for comparison.
rt-app mp3 100 n.a. 101 n.a. 45 n.a. 43 n.a.
Performance numbers are only applicable to periodic tasks.
rt-app 6% 100 85 103 85 31 60 33 59 rt-app 13% 100 76 102 76 39 46 41 50 rt-app 19% 100 64 102 64 93 54 93 54 rt-app 25% 100 53 102 53 93 43 96 45 rt-app 31% 100 44 102 43 115 35 145 43 rt-app 38% 100 35 116 32 113 2 140 29 rt-app 44% 100 -40k 142 -9k 141 -9k 145 -1k rt-app 50% 100 -100k 133 -21k 131 -22k 131 -4k
You need a special version of rt-app (depicted in EAS RFCv5 cover letter under [4]) which gives you additional columns (slack c_run c_period wu_lat) in the per task log file.
From EAS RFCv5 cover letter: 'The performance metric expresses the average time left from completion of the run period until the next activation normalized to best case: 100 is best case (not achievable in practice), the busy period ended as fast as possible, 0 means on average we just finished in time before the next activation, negative means we continued running past the next activation.
task performance = slack/(c_period - c_run) * 100
We calculate the average value out of all per-run period 'task performance' values for the the individual task and the average values of the tasks for the test run (equal workload if only 1 test run).
The rt-app performance numbers are not normalized against mainline.
[...]