1,433
edits
AM5728 Multimedia Performance Testbench: Difference between revisions
AM5728 Multimedia Performance Testbench (view source)
Revision as of 23:30, 1 June 2016
, 1 June 2016no edit summary
No edit summary |
No edit summary |
||
| Line 35: | Line 35: | ||
Different tools were used to measure the parameters specified in this test-bench. GstShark was the principal tool used to measure CPU load per core, frame rate and buffer processing time. GstShark is a benchmarking and profiling tool for Gstreamer pipelines developed by RidgeRun (If you want more information of this tool, please follow this link [https://developer.ridgerun.com/wiki/index.php?title=GstShark GstShark]). Top Linux command was used to measure memory consumption. Bandwidth application was used to measure memory bandwidth (If you want more information of this tool, please follow this link [http://zsmith.co/bandwidth.html Bandwidth]) . | Different tools were used to measure the parameters specified in this test-bench. GstShark was the principal tool used to measure CPU load per core, frame rate and buffer processing time. GstShark is a benchmarking and profiling tool for Gstreamer pipelines developed by RidgeRun (If you want more information of this tool, please follow this link [https://developer.ridgerun.com/wiki/index.php?title=GstShark GstShark]). Top Linux command was used to measure memory consumption. Bandwidth application was used to measure memory bandwidth (If you want more information of this tool, please follow this link [http://zsmith.co/bandwidth.html Bandwidth]). Video capture latency was measured using a special procedure developed in RidgeRun. | ||
= <span style="color:#008000">Multimedia Performance Test-bench Results</span><br> = | |||
In this section you will find the performance results obtained after applying the test-bench for each multimedia task. | |||
== <span style="color:#008080">AAC audio encode</span><br> == | |||