Is this the one you played with? I tried playing with this yesterday and gave up when I was unsure which platform I should select from the dropdown (was planning on searching for posts in this thread for any explanation of how to use the power estimator tool)
I have it set to Nano currently but where do I set it to 1024 GPU cores? The closest I got to your 7.6W figure was if I set GPU TPCs to 2 (CPU cores is already set to 4).
(if you know of any good comments in this thread explaining the power estimator tool and have it bookmarked, point me to that and I can try to pick up the rest)
I can walk you through it.
The top pulldown sets the Jetson board you're using. The Xaviers you can ignore. All Orin chips are the same hardware - AGX Industrial is the highest quality chip, so it has all of it's parts enabled, and enables the highest clock speeds. The other two AGX boards are the second highest quality, and the two of them should give you the same results. In fact, I think you get a little warning when you select the 32GB version saying just that. NX and Nano have variants, which they package up with different quantities of RAM.
For our purposes, you want to pick the smallest chip that has enough cores for you to test the config you want. That's gonna be the Orin AGX 32GB.
Don't worry about the Jetpack version. Orin's software comes with some preset power modes, that cap the power draw, and configure the hardware for specific use cases. You want everything on so you have total control - so set "Power Mode" to MAXN.
CPU settings should be straight forward - set your number of cores, and your clock speed. Note that you can't set arbitrary clock speeds, these are the clocks that Orin enables in firmware. Lower binned chips (like the Nano) turn off some high clock speeds, because they run too hot, and adds some extra low speeds that are very inefficient, but do offer tiny power savings where it really matters. Higher binned chips add some clock speeds at the top. If you want to experiment with those clocks, you'll need to change the chip you're working with, but the larger chips also have higher overhead, so be aware of it.
(a good way to show that is to make one configuration on NX, then make an identical config with AGX, and see the power draw differences)
The GPU widget doesn't configure cores, because you can't individually enable or disable GPU cores. You can't even individually disable SMs. SMs are in pairs inside of a TPC, and you
can enable and disable those. Each TPC is 256 CUDA cores (2 SMs at 128 cores apiece). Frustratingly, you'll notice that Orin doesn't support 6 TPCs. It supports 2, 3, 4, 7, and 8. Why this is true is a whole tangent not worth getting into, but the short version is that Orin organizes it's TPCs in a different way than Drake or RTX 30.
DLA and PVA are the "deep learning accelerator" and the "programmable vision array." This is hardware that Drake doesn't have so leave them off. Below them is the EMC widget. EMC = embedded memory controller. This is how fast the RAM goes. Orin has LPDDR5 memory, not the 5X that apparently is in Drake, so you can't actually set it to max Drake speed. You have two options, 3200Mhz (technically, 3199), which is full LPDDR5 speed, 102 GB/s, and 2133Mhz, which is ~66 GB/s, and underclocked MC
For handheld, I have long been assuming that Nintendo would run at the slower memory config, because 102GB/s is a
lot of bandwidth for a handheld. And I still think they will, but if they've gone with 5X, maybe they're pushing the chip hard enough that 66GB/s isn't enough in the the portable config, and they go up to 102 for handheld, 120 for docked. But I'm just guessing. Regardless, you only have a couple options.
Each widget has three load settings. "Low, Medium, High." Unfortunately, not a lot of clarity on exactly what that means for each one, but you get the rough idea. Modern hardware can run at full clock speed, but at reduced power usage when idle. Low load means the system is running at full clock, but presumably it's getting little enough work that it doesn't actually eat more power than just being idle. Medium is some load, but enough where power consumption is still less than max. High is "you're running this subsystem at full capacity for an extended period of time, this system cannot drain more power, I cannae do it cap'n"
Thraktor's own analysis set the systems to Medium, because we care about "Running the latest Zelda numbers" but it's basically impossible to hit peak usage on memory and GPU and CPU at the same time. If one of them is slammed to the gills, the others will eventually get stuck waiting on it, and start to idle out. I've done the same when I've played with it, but sometimes people come in with wildly low power numbers, based on "Low", so don't trick yourselves.
Also worth noting that the boxes tend to reset themselves in not obvious ways when you move one of the sliders. So be careful you haven't accidentally reset Memory Clock while you were playing with GPU load.
Estimate power at the bottom does what you expect, but the GUI is also usually updating in real time as you move sliders, so sometimes it looks like Estimate Power doesn't do anything. Reset sets it back to the defaults for MAXN, and "Download" lets you download a config file to put Orin into the configuration you've set, only useful to you if you want to save your settings for later fiddling.
Bookmarked!
