Geekbench is also very sensitive to lib versions.
When upgrading Rock 5B from Ubuntu Focal to Ubuntu Jammy guess what happens? According to Creepbench the board got around 10% slower 
- 10% difference when testing the little cluster only (grey is Ubuntu 20.04 Focal, blue 22.04 Jammy): https://browser.geekbench.com/v5/cpu/compare/16902259?baseline=16904879
- 12%/9.5% difference when testing the big cluster only (grey is Ubuntu 20.04 Focal, blue 22.04 Jammy): https://browser.geekbench.com/v5/cpu/compare/16902318?baseline=16904928
- 12.5%/8.5% difference when testing all cores (grey is Ubuntu 20.04 Focal, blue 22.04 Jammy): https://browser.geekbench.com/v5/cpu/compare/16902372?baseline=16905066
Three times tested and the results all hint at the same fact: you can’t use Geekbench for benchmarking 
EDIT: When comparing the Jammy (Armbian) image with Radxa’s Ubuntu other benchmarks also perform worse (e.g. 7-zip 11% slower):
| Distro | Clockspeed | Kernel | 7-zip | AES-128 (16 byte) | AES-256 (16 KB) | memcpy | memset |
|---|---|---|---|---|---|---|---|
| Focal arm64 | 2350/1830 MHz | 5.10 | 16450 | 683350 | 1337540 | 10830 | 29220 |
| Jammy arm64 | 2350/1830 MHz | 5.10 | 14660 | 665420 | 1339710 | 10230 | 29240 |
And the reason is simple: with the Armbian Jammy image memory latency is twice as high as with Radxa’s Ubuntu. That’s why sbc-bench contains both tinymembench and ramlat numbers (the latter also in Geekbench babysitting mode). See http://ix.io/48OL vs. http://ix.io/48PC