Jump to content

AM5728 Multimedia Performance Testbench: Difference between revisions

Line 59: Line 59:
[[Image:AM572x-testbench-AAC-exec-time.png|center|600px|AM572x-testbench-AAC-exec-time.png]]<br>
[[Image:AM572x-testbench-AAC-exec-time.png|center|600px|AM572x-testbench-AAC-exec-time.png]]<br>


In the chart above, is clearly shown that when using hardware acceleration, the total execution time of the AAC audio encode pipeline is significantly reduced. The average difference is 184.8 ms less in the pipeline execution time when the NEON&VFv4 extension is used.
In the chart above, is clearly shown that when using hardware acceleration (NEON&VFPv4 extension), the total execution time of the AAC audio encode pipeline is significantly reduced. The average difference is 184.8 ms less in the pipeline execution time when the NEON&VFv4 extension is used.
 
 
=== <span style="color:#0931C6">CPU load % per core</span><br>  ===
 
'''''Test pipeline:'''''
<pre style="background:#d6e4f1">
GST_TRACER_PLUGINS="cpuusage" gst-launch-1.0 filesrc location=/am5728-gst-tests/audio-samples/audio_sample.raw num-buffers=1000 ! audioparse ! faac ! fakesink sync=true -e
</pre>
 
'''''Obtained Results:'''''
[[Image:AM572x-testbench-AAC-cpuload.png|center|600px|AM572x-testbench-AAC-cpuload.png]]<br>
 
To measure this parameter, we used GstShark tool (developed by RidgeRun).
 
In the chart above, it can be seen that when using hardware acceleration (NEON&VFPv4 extension), no reduction is achieved in the CPU workload.
1,433

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.