July 29Jul 29 Sharing this here since it's a general-purpose tool rather than anything board-specific: GOESB is an open, reproducible benchmark for on-device speech-to-text — hash-verified results, official profiles + open packs so numbers are directly comparable across hardware, no account needed to submit. The problem it's trying to solve: if you're picking hardware for a local voice/STT workload, vendor numbers don't tell you much and blog posts go stale fast. GOESB is meant to be the place you can actually check "does this board run faster-whisper medium in real time, or do I need to drop to tiny and eat the accuracy hit." Right now the leaderboard is entirely x86 and Apple Silicon — Intel N150, an old Xeon, an Apple M1 Pro — because that's what we own. There isn't a single ARM/Rockchip result on it. If you're running Armbian on an RK3588 or RK3576 board (Orange Pi 5, NanoPC-T6, ROCK 5, NanoPi M5, whatever you've got), that's a genuine gap we can't fill ourselves. Worth being upfront: GOESB doesn't do RKNN/NPU acceleration today — it benchmarks faster-whisper, vosk, and whisper-cpp, all CPU-based (or CUDA/Metal where available). On a Rockchip board it runs as a plain ARM64 Linux machine, no NPU involved. Still a useful number — a clean CPU baseline — just not a substitute for NPU-accelerated inference. New runtime adapters (including an RKNN one, if anyone's interested) go in as reviewed, in-tree pull requests, not a plugin system, so that's open if anyone wants to take it on. Install and run: curl -fsSL https://raw.githubusercontent.com/taktx-io/GOESB/main/scripts/install.sh | sh goesb goesb with no arguments drops you into an arrow-key menu for picking a profile/pack and running + submitting — nothing to memorize. This is still very much a product in development. We've tested it on our own hardware, not the huge range of boards that show up on Armbian, so install or runtime hiccups on something we haven't seen are plausible. If it breaks, please file it on GitHub rather than just walking away from it — that's the fastest way to get it fixed for the next board. Have a look at https://www.goesb.com
July 30Jul 30 I had to install it like this, otherwise I get the error that goesb is not found. curl -fsSL https://raw.githubusercontent.com/taktx-io/GOESB/main/scripts/install.sh | sh Now you have RK3588 and QCS6490.
July 30Jul 30 Author Thank you very much! Our first external results, hopefully more will come. Pretty decent results considering these were CPU only. Will need to do some work on getting an adapter working which makes use of the NPU. Did the pip/pipx installation fail? Do you have the exact command that failed? Edited July 30Jul 30 by TaktX
July 30Jul 30 1 hour ago, TaktX said: Did the pip/pipx installation fail? Do you have the exact command that failed? There is no problem with the installation script itself. It's just that putting goesb at the end of the curl command threw an error "goesb not found". So I just removed goesb at the end of the curl command. I also ran the benchmark on a Phytium D2000. It wasn't recognized, and it said it will be uploaded as custom. I have to admit that outside of China it is a very rare ARM chip. https://www.tomshardware.com/news/mini-pc-has-phytium-CPU
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.