On 18/09/15 17:10, Leo Yan wrote:
[...]
No, still use "CPU0" for calibration. So below are my rt-app-6.json file, could you check if there still have other things i missed?
Sorry for i gave wrong json file, please see below code which is used for my profiling for rt-app-6 case:
{ "tasks": { "thread0": { "instance": 8, "loop": -1, "run": 120, "sleep": 0, "timer": { "ref": "unique", "period": 2000 } } }, "global": { "duration": 20, "calibration": "CPU0", "default_policy": "SCHED_OTHER", "pi_enabled": false, "lock_pages": false, "logdir": "./", "log_basename": "rt-app-6", "gnuplot": true } }
I assume here you run the tests with '"calibration": "CPU0"' ...
This is what you have to use in the calibration step prior to the actual tests. We always do this using the highest OPP on the big cpu on TC2 or JUNO so a 50% periodic task has run/period = 0.5 on a big cpu on the highest OPP.
This will give you a line like:
[rt-app] <notice> pLoad = 334ns : calib_cpu 0
Then you have to replace "CPU0" with 334 in your json files for the actual test step.
[...]