vingu-linaro
commented
2 years ago Hi Team, i have installed rt-app and my config.json doesn't have any pload in it.
when i rt-app config.json
it gives me different pload, sometimes 16 ns other times 19 ns etc.! why the pload is alterning is it calculating load on server or inserting certain real time delay on server ? is pload 16ns is better than 19ns. Apologies if this seems a silly question, kindly please help me in understanding it better .
"calibration" can get 2 kinds of value. In you case, calibration: "CPU0" means that we will calibrate the run loop on CPU0. Before starting the scenario, the algorithm will compute the time to execute run 1 loop and will try to filter all possible sources of variations (freq scaling and cpufreq governor, hyperthreading, thermal mitigation, heterogeneous platform) to get the maximum compute capacity (ie lowest duration). Nevertheless, it's sometimes difficult to always get the same calibration from one run to another and you can see some difference between two calibration depending of what is running beside rt-app. If you plan to run several time your test on the same platform and you want to compare the results, you can set the pload duration in "calibration" field directly after few iteration. Usually you should use the lowest pLoad which reflects the highest achievable performance of your system.
In your case I would suggest to set "calibration": 16
what i'm trying to do is to run a container using docker swarm and kubernetes and wanted to see which orchestration is better in load / spinning up a container .! The same stuff again after installing rt-patch
Also, Can you let me know if my understanding is right? period is total time duration that we set for a particular task. due to wu_lat the period that we set (10,000) could vary .! rel_st is the time at which the task actually began due to latency and run is the total time it took to complete the task.!
Yes the period is the total duration between 2 call of the "timer": { ... }
The statistics in log file are relative to a phase. It means that rel_st is the relative start time of a phase "light", "heavy", "light2", "heavy2" since the beg of the run wu_lat is the sum of wakeup latency in a phase so it's wakeup latency of your timer in your case.
Here is my config file, FYI (which isn't written by me rather understood up to certain extent by going through tutorial)
suravarapusuryakiran
Hi Team, i have installed rt-app and my config.json doesn't have any pload in it.
when i rt-app config.json
it gives me different pload, sometimes 16 ns other times 19 ns etc.! why the pload is alterning is it calculating load on server or inserting certain real time delay on server ? is pload 16ns is better than 19ns. Apologies if this seems a silly question, kindly please help me in understanding it better .
what i'm trying to do is to run a container using docker swarm and kubernetes and wanted to see which orchestration is better in load / spinning up a container .! The same stuff again after installing rt-patch
Also, Can you let me know if my understanding is right? period is total time duration that we set for a particular task. due to wu_lat the period that we set (10,000) could vary .! rel_st is the time at which the task actually began due to latency and run is the total time it took to complete the task.!
Here is my config file, FYI (which isn't written by me rather understood up to certain extent by going through tutorial)