• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 310 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA2EVM5777: TIDL Latency is too high

Taekmin Lee
Expert 1445 points

Part Number: TDA2EVM5777

Hi.

I am working on changing the TIDL network input size.

I found something strange when I was testing a TIDL network of different input sizes.

The Latency of the TIDL Algorithm at the NullSource link input looks like normal.

But, The Latency of the TIDL Algorithm in some network Capture link inputs looks like abnormal.

There are no performance differences in FPS, only Latency.

I'm just change the input source NullSource to Capture.

The network input sizes are 576x240 (normal) and 576x226 (abnormal).

Maybe, does the aspect ratio affect Latency?

The input source(NullSource/Cature) size is 1280x720 and has been resized using VPE.

Attached is a latency log file (Excel) that I have arranged for easy viewing.

TIDL_LatencyLog.xlsx

Give me a hint to solve this problem.

Regards,

Lee.

  • 0
    TI__Genius 15985 points

    Hi,

    It should not depend on aspect ratio.

    srcTolinklatency should be addition of the same of previous link plus local link latency of current link.

    In the working case if you add srcTolinklatency of ipc in link and add local link latency of tidl then it will somehow match with tidl srcTolinklatency value.

    There is something going wrong with calculation.

    And as per shared latency which is more than 500 ms tidl tildl link only, you should get less than 2 FPS for each eve. So in total less than 8 FPS using all 4 eve cores.

    And i hope you are getting around 20, so ther is some calculation is going wrong.

    Regards,

    Anuj