4 ms·
Many, since it's been out in the LicheePi4A for a while. Similar to Pi 4. On my primes benchmark it comes in (at 1.848 GHz) at 10.43 seconds vs 12.1 for a Pi 4
by brucehoult 3y ago
Many, since it's been out in the LicheePi4A for a while. Similar to Pi 4.
On my primes benchmark it comes in (at 1.848 GHz) at 10.43 seconds vs 12.1 for a Pi 4 running A64 code.
The other common RISC-V SoC right now, the JH7110, which is on quite a bit cheaper boards such as the VisionFive 2 and Pine64 Star64 and Milk-V Mars, comes in at 14.9 seconds. That's more or less an A55 equivalent.
https://hoult.org/primes.txt https://hoult.org/primes.txt
- imtringued 3y agoYour benchmark is near useless but I appreciate that you have benchmarked a variety of systems. Thanks.
- brucehoult 3y agoYou try coming up with something that you can run on an AVR and an i9!! I submit that it is no worse than Dhrystone or Coremark, and correlates well with those while being a lot less code. It is better than those at being impervious to tricky compiler or library optimisations -- I have seen for example libc string function implementations that unroll a loop processing 32 bit words 5 times, not 4 or 8. Why? Well, Dhrystone just happens to call that function with an 18 byte string. Every time. Ugh. They all exercise just the CPU core (load/store, arithmetic, branching) and L1 caches or SRAM. Which is not a full-system test, but is valuable information.