Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

yamitranscode gives 10-15% performance difference from run to run #96

Open
dvrogozh opened this issue May 25, 2017 · 2 comments
Open

yamitranscode gives 10-15% performance difference from run to run #96

dvrogozh opened this issue May 25, 2017 · 2 comments

Comments

@dvrogozh
Copy link

dvrogozh commented May 25, 2017

Consider running the following:

for i in `seq 1 20`; do
/usr/bin/time -f "%e;%U;%S;%P" -a --output="log.txt" \
yamitranscode \
  -i input_1920x1080p.264 \
  -o out.264 \
  -W 1920 -H 1080 \
  -c AVC \
  -ipperiod 1 \
  -intraperiod 30 \
  --rcmode CQP \
  -qp 25
done

On SKL NUC I observe:

$ cat log_.txt
17.53;1.62;1.26;16%
15.62;1.65;1.24;18%
17.35;1.62;1.24;16%
15.63;1.65;1.28;18%
17.33;1.65;1.25;16%
15.63;1.63;1.28;18%
17.36;1.63;1.24;16%
15.63;1.69;1.22;18%
17.35;1.66;1.23;16%
15.63;1.72;1.22;18%
17.35;1.69;1.19;16%
15.63;1.65;1.26;18%
17.35;1.66;1.21;16%
15.61;1.65;1.27;18%
17.34;1.67;1.22;16%
15.63;1.68;1.24;18%
17.35;1.65;1.22;16%
15.63;1.68;1.23;18%
17.34;1.63;1.23;16%
15.65;1.69;1.26;18%
17.35;1.65;1.24;16%

Looks like yamitranscode has 10-15% variations in performance from run to run.

@xuguangxin
Copy link
Contributor

Hi @dvrogozh
Sorry for late.

I tried this on my SKL 3 times, the output is stable. Is any high load thing in your machine? Or did you lock your machine frequency?

thomas@zion:~/projects/yami/tmp/739/libyami-utils$ cat log.txt

0.51;0.01;0.06;14%
0.51;0.03;0.04;14%
0.51;0.02;0.05;14%
0.50;0.02;0.04;14%
0.51;0.02;0.06;15%
0.50;0.04;0.03;14%
0.50;0.03;0.04;14%
0.50;0.02;0.04;14%
0.50;0.02;0.05;14%
0.50;0.03;0.04;14%
0.51;0.03;0.04;14%
0.50;0.03;0.04;14%
0.50;0.03;0.04;14%
0.50;0.02;0.04;14%
0.50;0.02;0.05;14%
0.50;0.03;0.04;14%
0.51;0.03;0.04;15%
0.50;0.04;0.03;14%
0.51;0.03;0.04;14%
0.50;0.03;0.03;14%
0.50;0.03;0.03;14%
0.51;0.03;0.04;14%
0.50;0.04;0.02;14%
0.51;0.03;0.04;14%
0.50;0.02;0.05;14%
0.51;0.03;0.04;14%
0.50;0.02;0.05;14%
0.50;0.02;0.05;14%
0.51;0.03;0.04;14%
0.50;0.03;0.04;14%
0.51;0.04;0.03;14%
0.51;0.04;0.03;14%
0.50;0.04;0.02;14%
0.50;0.01;0.06;14%
0.50;0.04;0.03;14%
0.50;0.04;0.03;14%
0.51;0.03;0.04;15%
0.50;0.03;0.04;14%
0.51;0.04;0.03;14%
0.50;0.03;0.04;14%

@xuguangxin
Copy link
Contributor

xuguangxin commented Jun 19, 2017

hi @dvrogozh ,
I tried some clips little longer. I can find 1% cpu variations . This may introduce by my tmux. I checked cpu usage using top, the tmux will use 0%~1% cpu.

17.87;1.49;0.66;12%
18.03;1.49;0.73;12%
18.14;1.52;0.71;12%
18.21;1.52;0.69;12%
18.19;1.58;0.58;11%
17.91;1.50;0.68;12%
18.15;1.51;0.69;12%
17.97;1.65;0.57;12%
18.07;1.62;0.59;12%
18.10;1.54;0.67;12%
17.94;1.53;0.66;12%
18.00;1.55;0.66;12%
17.93;1.57;0.65;12%
18.26;1.52;0.67;12%
18.12;1.52;0.65;12%
17.89;1.48;0.68;12%
18.15;1.52;0.64;11%
18.19;1.54;0.62;11%
18.17;1.56;0.66;12%
18.00;1.52;0.70;12%

But when we check the frame rate. the variation is below 0.5%
Since we done all decode/encode things on gpu, the cpu usage is not so important. right?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants