-
-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
get Jetson GPU Information #476
Conversation
Thank you for this! I really appreciate it! I just have a couple questions since I don't have a Jetson device to test myself. The VRAM being displayed is the same as the memory of the entire system, right? Is there any benefit to this chart that the system memory chart doesn't provide? Referencing the example We talked about maybe using |
data := string(output) | ||
ramPattern := regexp.MustCompile(`RAM (\d+)/(\d+)MB`) | ||
gr3dPattern := regexp.MustCompile(`GR3D_FREQ (\d+)%`) | ||
tempPattern := regexp.MustCompile(`([a-z0-9_]+)@(\d+\.?\d*)C`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can use gpu@(\d+\.?\d*)C
here to target the gpu temp?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm using an AGX Orin.
This is the tegrastats output:
01-24-2025 09:56:48 RAM 4300/30698MB (lfb 197x4MB) SWAP 28/15349MB (cached 0MB) CPU [0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729,0%@729] EMC_FREQ 0%@2133 GR3D_FREQ 0%@[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off OFA off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 [email protected] iwlwifi_1@43C [email protected] [email protected] [email protected] [email protected] VDD_GPU_SOC 2171mW/2171mW VDD_CPU_CV 241mW/241mW VIN_SYS_5V0 4375mW/4375mW
I will check the code. And try to test it with more versions of Jetson
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, it looks like for power you have VDD_GPU_SOC 2171mW
, VDD_CPU_CV 241mW
, and VIN_SYS_5V0 4375mW
.
On Orin Nano they have VDD_IN 12479mW
, VDD_CPU_GPU_CV 4667mW
, and VDD_SOC 2817mW
.
Annoying that they are different, but I guess we have to pick the best option for each model.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found this. It looks like Orin Nano and Orin NX do not have separate power monitors for CPU and GPU.
If you don't want to work on this anymore I think what you have is fine. Those models can't get GPU temperature. Later I can add a fallback for total system power and use VDD_IN
for them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hhhh,jetson does have a lot of versioning issues and it's killing us too, we have a lot of Jetson but it's the new year,so I can test it later in the year!
I just tried this on my Orin Nano and this is what I see when running gpu-burn. |
@Links17 I merged this but changed the commit author so you would get credit as a contributor (your email was empty in the original commit). This PR isn't picking up the merge so I'm just going to close it. I made changes that I can't test myself, so if it's possible for you and/or @silven to test, that would be a huge help. You can pull changes from the main branch, or clone and build the agent: # Clone the repository
git clone --depth 1 https://github.com/henrygd/beszel.git
# Navigate to the project directory
cd beszel/beszel
# Builds the agent only (check build folder in current directory)
make build-agent Thank you! |
Getting Jetson GPU Information with tegrastats
Test: