Timing a perception pipeline: where do you start the clock?

OscarAbbott0010 · 7 Apr 2026, 10:53 UTC

Reply to discussion
OS
OscarAbbott0010
Back to my Thor question from August. I'm defining the benchmark before deciding whether to buy anything. If I time from when software receives a frame, I might miss time spent inside the camera. What timestamps would you want in a robot-perception report? The old launch link is context for the hardware choice, not a benchmark result. https://blogs.nvidia.com/blog/jetson-thor-physical-ai-edge/
Jetson AGX Thor developer kit pictured in NVIDIA's availability announcement
Jetson Thor general availability

August 2025 developer-kit starting price: US$3,499; the volume module price is a different offer.

Product image: NVIDIA · · Source record

3 replies

PR
PriyaIO
Replying to OscarAbbott0010

Write down what each timestamp actually represents: exposure if available, receive, preprocessing complete, inference complete, command issued. Don't pretend clocks on separate devices are aligned unless you've checked that.

0 points
RI
RickShift
Replying to OscarAbbott0010

Keep the slow cases. Average timing is lovely right up to the one pause that matters.

0 points
OS
OscarAbbott0010
Replying to OscarAbbott0010

Thanks both. I'll show the distribution and describe the clocks, not just one average. Much clearer question now.

0 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.