# Coremark benchmark degradation on HiFive Unmatched

**URL:** <https://forums.sifive.com/t/coremark-benchmark-degradation-on-hifive-unmatched/5193>\
**Category:** HiFive Unmatched\
**Created:** [September 21, 2021, 10:24am UTC](https://forums.sifive.com/t/coremark-benchmark-degradation-on-hifive-unmatched/5193 "2021-09-21T10:24:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![vmedea](https://avatars.discourse-cdn.com/v4/letter/v/3be4f8/32.png) [@vmedea](https://forums.sifive.com/u/vmedea)\
**Post date:** [September 21, 2021, 11:01am UTC](https://forums.sifive.com/t/coremark-benchmark-degradation-on-hifive-unmatched/5193/2 "2021-09-21T11:01:28Z")

</div>

The output of that command here is

```auto
$ uname -r
5.13.9-00012-g71cf60a44907
$ ./coremark.exe 
2K performance run parameters for coremark.
CoreMark Size : 666
Total ticks : 13309
Total time (secs): 13.309000
Iterations/Sec : 4508.227515
Iterations : 60000
Compiler version : GCC10.3.0
Compiler flags : -O2 -DPERFORMANCE_RUN=1 -lrt
Memory location : Please put data memory location here
                        (e.g. code in flash, data on heap etc)
seedcrc : 0xe9f5
[0]crclist : 0xe714
[0]crcmatrix : 0x1fd7
[0]crcstate : 0x8e3a
[0]crcfinal : 0xbd59
Correct operation validated. See README.md for run and reporting rules.
CoreMark 1.0 : 4508.227515 / GCC10.3.0 -O2 -DPERFORMANCE_RUN=1 -lrt / Heap

```

Mine is running at 1.4Ghz so **Coremark/MHz** is 3.2. Still, not close to the 5.1 reported on that page. I wonder under what conditions it was measured.

---

_[View the full topic](https://forums.sifive.com/t/coremark-benchmark-degradation-on-hifive-unmatched/5193)._