4 ms·
The architectural details here were pretty interesting: https://moonbaseotago.github.io/talk/index.html https://moonbaseotago.github.io/talk/index.html It wou
by Symmetry 5y ago
The architectural details here were pretty interesting:
https://moonbaseotago.github.io/talk/index.html https://moonbaseotago.github.io/talk/index.html
It would be nice to get actual performance numbers rather than just frequency scaled Dhrystone but I suppose we have to be patient.
- Taniwha 5y agoDhystone's just a place to start, it helps me make quick tweaks, and I'm at that stage of the process - it's particularly good because it's somewhat at odds with my big wide decoders - VRoom! can decode bundles of up to 8 instructions per clock, while Dhrystone has lots of twisty branches, only decodes ~3.7 instructions per bundle - it's a great test for the architecture by pushing at the things it might not be as good as. Having said that I'm about reaching the end of the point where it's the only thing - being able to run bigger longer benchmarks is one of the reasons for bringing up linux on the big FPGA on AWS
- Taniwha 5y agoI'll add that freq scaled Dhrystone (DMIPS/MHz) is a particularly useful number because it helps you compare architectures rather than just clocks - you can figure out questions like "If I can make this run at 5GHz how will it compare with X?"
- brucehoult 5y agoYou could use verilator simulating VRoom! as a benchmark. I haven't actually looked at the generated code, but I imagine it's thousands upon thousands of instructions in a row with no conditional branching at all. CHOMP.