First impressions and thoughts on the GTR9 Pro (Beelink's 395)

Posted by kmouratidis@reddit | LocalLLaMA | View on Reddit | 30 comments

tl;dr: Good and bad, some "benchmarks" and details here. Not sure I'd recommend it. Not yet.

Hey y'all! Just like many others I wanted to try the 395, but since I mostly wanted it as a server first (and LLM runner third), I wanted one with 10 Gbps networking. The MS-S1 hadn't come out yet, so I went with the Beelink GTR9 Pro AMD Ryzen™ AI Max+ 395, and \~25 days later it's here.

I tried the preinstalled Windows, which functioned for a bit, quickly devolved into a mess that made me want to return it. Thankfully, I wanted it as a server, which means I'll be running Linux, but I had to test it. Plenty of crashes under load, the Intel network card not working, and other weirdness. Turns out there are plenty of known issues that may be hardware or driver related, plenty of posts and speculation in r/BeelinkOfficial and it has been going for a couple weeks it seems, and may also affect Linux, but oh well, time to move on.

People suggest you use Fedora or Debian Sid, or anything with a recent kernel, and that's probably good advice for most people, but I ain't running Fedora for my server. I used a heavily configured DietPi (so basically Debian) instead, for no other reason than consistency with the rest of my (actually mini*) servers. Surely the driver situation can't be that bad, right? Actually yes, it's perfectly fine to run Debian and I haven't had an issue yet, although it's early, let's see if it reach even 10% the uptime my TrueNAS server has. After troubleshooting a few issues, installing the (hopefully) correct drivers, and building llama.cpp (lemonade and vLLM will have to wait until the weekend), I quickly tested a bunch of models, and the results I'm getting seem to roughly align with what others are getting (1, 2, 3, 4). I have documented everything in the gist (I think!).

Out of the box, the Beelink runs with 96GB allocated as VRAM and can consume up to 170W without me messing with BIOS or Linux settings. In short, the results are exactly as you would expect:

Model Size Params Backend Test Tokens/s (FA 0) Tokens/s (FA 1)
GLM-4.5-Air (Q4_K_XL) 68.01 GiB 110.47B ROCm pp512 142.90 ± 1.39 152.65 ± 1.49
tg128 20.31 ± 0.07 20.83 ± 0.12
Qwen3-30B (Q4_K_XL) 16.49 GiB 30.53B ROCm pp512 496.63 ± 11.29 503.25 ± 6.42
tg128 63.26 ± 0.28 64.43 ± 0.71
GPT-OSS-120B (F16) 60.87 GiB 116.83B ROCm pp512 636.25 ± 5.49 732.70 ± 5.99
tg128 34.44 ± 0.01 34.60 ± 0.07

Happy to run tests / benchmarks or answer questions, but some stuff may need to wait for the weekend.

----------

* Bonus: I sent this photo of the Beelink with my old Minisforum Z83-F to someone, joking about how mini PCs looked in 2015 vs in 2025. She thought the Minisforum was the one from 2025.

[Beelink GTR9 Pro (2025) dwarfs it's little bro, the Minisforum Z83-F (2015)](