Comments URL: https://news.ycombinator.com/item?id=50265594

Points: 169

# Comments: 92

Comments URL: https://news.ycombinator.com/item?id=48338979

Points: 13

# Comments: 1

We could debate about strict definitions all day, but I think the vast majority of people differentiate between a Raspberry Pi 5 (not a great example given it needs storage, pick anything with eMMC if you truly want everything on a single board) running a full Debian-based OS, and a Pico running MicroPython (or whatever your poison of choice is) and one task at a time, at least I do when it comes to this kind of thing!

For the 2nd, the file I grabbed initially was https://github.com/geerlingguy/ai-benchmarks/blob/main/obenc... - which I now notice wasn't modified in his repository, so I can check that out, but either way, the same version has been tested across everything thus far.

Armbian do a great job of handling support for a whole host of boards (including most I included in this list), so you'll usually have Debian/Ubuntu-based flavours. Vendor kernels and vendor supplied images will be hit and miss. Mainline Linux support is a flag you filter by on the benchmark comparison site linked in the article, but it's a difficult one to keep up to date and define exactly. It could have some kind of support, but miss out on display functionality, or WiFi yada yada. What would we then class as having mainline support? All hardware etc functioning? If so, very, very few will meet that definition.

I get the desire for the information, and perhaps I should have envisioned these types of questions, but all I initially meant for the post to be was a recap for people following me to see which boards I'd tested that were released last year :D

I don't know if I'd release everything as is, there's a lot of hard coded nonsense that I'd need to filter out and after testing 80 boards, I have a bunch of improvements I want to make. Opening up the test scripts to others isn't/wasn't a high priority item, as I didn't even plan on making this site initially :D

Room temperature data is also nice, but I'll need to draw a line somewhere, on average these tests take around 3-4 hours to run, and with 80 boards right now, best case scenario is 10 straight days of testing (in reality, more with setup and.. life). I could use data on the most popular boards and only do a handful, but I probably have to limit the scope at this point and clearly state the testing conditions and how it may differ in your real world setup.

I can definitely do more to expand on the testing process though, and I can look at sharing the exact commands that are run with my automation so that users can at least mimic the benchmark runs if not the full automation. I really appreciate the responses and feedback, though, so thank you!

Otherwise, there are dual NVMe HATs for the Raspberry Pi 5 but you'll be splitting a single PCIe Gen 2 lane across both drives (unless you go for the much more expensive HATs that have a Gen 3 PCIe switch on them to then share a single Gen 3 lane across them!)