@dburns: There are more CUDA cores in the Xavier. If you do video rendering which uses CUDA cores, then video would also be faster on Xavier versus TX2. The exact fuzzy answer is that “it depends on the video data and screen format” whether or not there is a big video speed increase when moving to Xavier. One very important upgrade by going to Xavier is RAM quantity…typically OpenGL or other apps will use the same amount of video RAM regardless of whether the video card has extra or not. However, many CUDA models will consume everything they can get, and so RAM quantity probably matters more when working with CUDA (unless you use your Xavier for profession CAD and rendering).
@cudaeducation: The 1050 Ti has far more cores. This will almost always beat an embedded device. However, your 1050 is probably using ten times the power the Xavier uses when rendering the same thing. There is a reason you will see many posts saying “train on the desktop PC, run the model on the Xavier”. The trick is to have models run inference (not training) sufficiently fast for small footprint and low power consumption…imagine the difference between using a Jetson with a drone versus a desktop PC motherboard. The battery alone would be killer (you probably need a car battery to put a desktop PC graphics card on a drone).
Jetsons have a number of independently adjustable clocks and features for which cores are active or not. This is basically the DVFS table. The concept of a “model” (from “nvpmodel”) is one of limiting which cores are available and limiting what max or min clock frequency is available. Some people don’t need max performance, but they do need longer battery life. Nvpmodel is a way to pick table limits. Model “-m 0” is max in that it allows max clock frequencies and cores active. It is jetson_clocks.sh which says to go to max frequency, but if the model does not first set the DVFS to its fastest allowed clock, then jetson_clocks.sh won’t actually achieve max performance…it’ll only achieve max for that model. Fastest model, followed by implementing max clocks of that model is what this does to run “nvpmodel -m 0” followed by “jetson_clocks.sh”.