Semiconductor & Computer Engineering
(Added one core coremark result) |
|||
| (5 intermediate revisions by 5 users not shown) | |||
| Line 5: | Line 5: | ||
'''CoreMark/MHz''' is a measurement of [[single thread performance]] per [[clock frequency]]. The number is based on the [[CoreMark]] [[benchmark]] score. It is obtained by taking the single-core [[CoreMark]] number and dividing it by the [[clock speed]] used when the benchmark is performed. | '''CoreMark/MHz''' is a measurement of [[single thread performance]] per [[clock frequency]]. The number is based on the [[CoreMark]] [[benchmark]] score. It is obtained by taking the single-core [[CoreMark]] number and dividing it by the [[clock speed]] used when the benchmark is performed. | ||
| − | While CoreMark is a relatively simple benchmark that addresses some of the deficiencies with [[Dhrystone]], it has been designed around embedded applications and therefore demonstrates highly favorable numbers for relatively simple designs (e.g., [[dual-issue]] [[in-order]]) while having weaker performance scaling in complex designs (e.g., [[out-of-order]] [[superscalar]]). Therefore it may sometimes show that a very well-design in-order core achieves >80% the performance of very complex high-performance OoO cores while real-world applications will demonstratively show significantly bigger gaps and discrepancies. Additionally, since the score is | + | While CoreMark is a relatively simple benchmark that addresses some of the deficiencies with [[Dhrystone]], it has been designed around embedded applications and therefore demonstrates highly favorable numbers for relatively simple designs (e.g., [[dual-issue]] [[in-order]]) while having weaker performance scaling in complex designs (e.g., [[out-of-order]] [[superscalar]]). Therefore it may sometimes show that a very well-design in-order core achieves >80% of the performance of very complex high-performance OoO cores while real-world applications will demonstratively show significantly bigger gaps and discrepancies. Additionally, since the score is normalized by [[clock frequency]], it cannot be used to derived absolute performances. Furthermore, since it's possible to achieve higher CoreMark at considerably lower frequency through well-known techniques such as shortening the pipeline which saves a significant amount of silicon, using CoreMark/MHz per unit area to derive area-efficiency is problematic. |
== Scores == | == Scores == | ||
| Line 28: | Line 28: | ||
| [[Arm]] || {{armh|Cortex-M23|l=arch}} || || {{arm|ARMv8-M}} Mainline || 2.64 | | [[Arm]] || {{armh|Cortex-M23|l=arch}} || || {{arm|ARMv8-M}} Mainline || 2.64 | ||
|- | |- | ||
| − | | [[OnChip]] || | + | | [[OnChip]] || [[Apicalis]] || || {{riscv|RV32IM}} || 2.7 |
|- | |- | ||
| [[Arm]] || {{armh|Cortex-M1|l=arch}} || || {{arm|ARMv6-M}} || 1.85 | | [[Arm]] || {{armh|Cortex-M1|l=arch}} || || {{arm|ARMv6-M}} || 1.85 | ||
| Line 45: | Line 45: | ||
|- | |- | ||
| [[Arm]] || {{armh|Cortex-R52|l=arch}} || || {{arm|ARMv8-R}} || 4.2 | | [[Arm]] || {{armh|Cortex-R52|l=arch}} || || {{arm|ARMv8-R}} || 4.2 | ||
| + | |- | ||
| + | | [[Arm]] || {{armh|Cortex-R82|l=arch}} || || {{arm|ARMv8-R}} || 5.82 | ||
|- | |- | ||
| [[SiFive]] || {{sifive|E20|l=arch}} || || {{riscv|RV32IMC}} || 2.51 | | [[SiFive]] || {{sifive|E20|l=arch}} || || {{riscv|RV32IMC}} || 2.51 | ||
| Line 70: | Line 72: | ||
| [[UC Berkeley]] || {{ucberkeley|BOOMv2|l=arch}} (4-way) || || {{riscv|RV64IMAFD}} || 4.7 | | [[UC Berkeley]] || {{ucberkeley|BOOMv2|l=arch}} (4-way) || || {{riscv|RV64IMAFD}} || 4.7 | ||
|- | |- | ||
| − | | [[Western Digital]] || [[SweRV EH1]] || || {{riscv|RV32IMC}} || | + | | [[Western Digital]] || [[SweRV EH1]] || || {{riscv|RV32IMC}} || 5.78 |
| + | |- | ||
| + | | [[Western Digital]] || [[SweRV EH2 single thread]] || || {{riscv|RV32IMC}} || 6.03 | ||
|- | |- | ||
| − | | [[Western Digital]] || [[SweRV EH2 | + | | [[Western Digital]] || [[SweRV EH2 two threads]] || || {{riscv|RV32IMAC}} || 7.83 |
|- | |- | ||
| − | | [[Western Digital]] || [[SweRV | + | | [[Western Digital]] || [[SweRV EL2]] || || {{riscv|RV32IMC}} || 4.33 |
|- | |- | ||
| − | | [[ | + | | [[Alibaba]] || [[XT910]] || July 25, 2019 || {{riscv|RV64GCV}} || 7.1 |
|} | |} | ||
Latest revision as of 10:32, 16 June 2022
CoreMark/MHz is a measurement of single thread performance per clock frequency based on the CoreMark benchmark.
Overview[edit]
CoreMark/MHz is a measurement of single thread performance per clock frequency. The number is based on the CoreMark benchmark score. It is obtained by taking the single-core CoreMark number and dividing it by the clock speed used when the benchmark is performed.
While CoreMark is a relatively simple benchmark that addresses some of the deficiencies with Dhrystone, it has been designed around embedded applications and therefore demonstrates highly favorable numbers for relatively simple designs (e.g., dual-issue in-order) while having weaker performance scaling in complex designs (e.g., out-of-order superscalar). Therefore it may sometimes show that a very well-design in-order core achieves >80% of the performance of very complex high-performance OoO cores while real-world applications will demonstratively show significantly bigger gaps and discrepancies. Additionally, since the score is normalized by clock frequency, it cannot be used to derived absolute performances. Furthermore, since it's possible to achieve higher CoreMark at considerably lower frequency through well-known techniques such as shortening the pipeline which saves a significant amount of silicon, using CoreMark/MHz per unit area to derive area-efficiency is problematic.
Scores[edit]
Note that some values were taken as reported by the chip designers while other values were calculated by WikiChip.