+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Edge AI & Gadgets (https://www.datasculpting.ai/inference/forumdisplay.php?fid=21)
+--- Forum: SBCs / Mini PCs (https://www.datasculpting.ai/inference/forumdisplay.php?fid=74)
+--- Thread: Jetson still a thing (/showthread.php?tid=44)
Pages:
1
2
Jetson still a thing - phasespark - 08-28-2026
Spent some time on this today and wanted to compare notes.
I've gone back and forth between PyTorch and Ollama for Kimi. The interesting difference for me has been router policy.
Interested in tradeoffs more than fan loyalty.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Re: Jetson still a thing - oxiderunner - 08-28-2026
Good point. The pattern around tokens/sec has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Re: Jetson still a thing - dockkite69 - 08-28-2026
Quote:Good point. The pattern around tokens/sec has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make t
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefill/decode split. Not glamorous advice, but repeatable baselines save a lot of time.
Re: Jetson still a thing - promptfield - 08-28-2026
That matches what I was seeing. The pattern around embeddings has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: Jetson still a thing - cachebench - 08-31-2026
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Re: Jetson still a thing - mintquill - 09-01-2026
What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: Jetson still a thing - cobalttinker - 09-01-2026
Quote:What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lo
Need a little more detail here. What model, what runtime, and roughly what context size?
Re: Jetson still a thing - homelabhenry - 09-01-2026
Thanks, that helps. I ended up in about the same place using llama.cpp. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Re: Jetson still a thing - byteyard - 09-01-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there.
Re: Jetson still a thing - batchfield55 - 09-01-2026
That matches what I was seeing. That matches what I saw on 7900 XTX. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.