Multiple Jetson board for computing power


I’m developing multiple cameras application with Jetson Xavier DV kit.
the goal is to implement real time image processing (such as panoramic stitching).
Since I’m using three of 4K cameras, it is little bit hard to get this performance.
having a time for optimization with one board, I’m wondering if there is an option to use multiple Jetson boards.


Thank you for your advises.


Do you want to mount multiple camera on a single Xavier(ex. master) or separate them on several boards?

One key problem of stitching is synchronization.
Suppose you expect to have the three 4K image at the same time, mount camera in different device will make it more challenge.

However, based on the spec, a single Xavier can only support 2x 4Kp60 decode.

If the synchronized issue can be overcome, to leverage the computing power of other Jetson is possible.
But expected there is some transmission overhead which will reflect on latency.


Thank you AastaLLL.
regarding encoding specification, sychronization, Let’s say I will connect multiple cameras on master Jetson, and encoding will be panoramic video resized to 4K resolution.

the purpose is to process it in real-time, and if there is enough resources left, there will be more functions.

" leverage the computing power of other Jetson is possible "

  1. How can I get some information regarding this topic?
  2. Can I just use Jetson Xavier DV kit + Jetson board(without other kit?
    or should be Dual Jetson Xavier DV kit?


We have several camera interface API.
For example, you can check this document for some information:

The problem is that the maximal decode/encode power of a single Xavier is 2x4Kp60.
The performance of 3x4Kp60 camera on a single Xavier is not guaranteed.



  1. I meant using Multiple Jetson board to increase computing power. I cannot find related topic in the link. did you mean there’s one in the link?

  2. Oh, I got it. maybe we should resize input cameras resolution too.


How can the synchronization problem be overcome?

Please check this one:


A possible software solution is to attach a timestamp to input frame.
And implement a stitch algorithm to compensate the slightly time-shift.