Skip to content

Commit f2bcf80

Browse files
authored
Merge pull request #667 from ckormanyos/benchmark_docs
2 parents 820da7e + 9e01136 commit f2bcf80

1 file changed

Lines changed: 14 additions & 13 deletions

File tree

ref_app/src/app/benchmark/readme.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ The benchmark used is a ${\sim}100$ decimal digit AGM $\pi$ calculation.
8383

8484
| Target | runtime $[ms]$ | relative |
8585
|--------------------|-----------------|------------|
86-
| `am6254_soc_` | 0.37 | 1.0 |
86+
| `am6254_soc` | 0.37 | 1.0 |
8787
| `am335x` | 1.5 | 4.1 |
8888
| `stm32f446` | 5.1 | 14 |
8989
| `rpi_pico2_rp2350` | 6.3 | 17 |
@@ -97,31 +97,32 @@ for the $8$-bit MICROCHIP(R) AVR controller of the ARDUINO
9797
and the $32$-bit ARM(R) 8 controller
9898
of the BeagleBone Black Edition, Rev. C.
9999
The $\pi$ calculation requires approximately
100-
$420~\text{ms}$ and $1.5~\text{ms,}~$
100+
$410~{\text{ms}}$ and $1.5~{\text{ms,}}$
101101
respectively, on these two microcontroller systems.
102102

103-
The $64$-bit ARM(R)v8-a (i.e., Cortex(R) A53) performs the
104-
calculation (running on one single A53 core of the PocketBeagle2 board)
105-
in $0.37~\text{ms.}$
103+
The $64$-bit ARM(R) v8-a (i.e., Cortex(R) A53) performs the
104+
calculation in $0.37~{\text{ms}}$. This benchmark runs
105+
on _one_ _single_ A53 core of the PocketBeagle2 board and there
106+
are $3$ additional identical A53 cores (and $2$ smaller ones)
107+
simply waiting in idle loops.
106108

107109
The $32$-bit ARM(R) Cortex(R) M4F controller on
108110
the `stm32f446` board performs the calculation in
109-
the middle of the two extremes, with a result
110-
of $5.1~\text{ms}$.
111+
the middle of these extreme performance classes,
112+
with a result of $5.1~{\text{ms}}$.
111113

112114
The $32$-bit RISC-V controller (having a novel _open-source_ core)
113115
on the `wch_ch32v307` board boasts a quite respectable
114-
time of $8.0~\text{ms.}$
116+
time of $8.0~{\text{ms}}$.
115117

116118
Running on only one core (core0) of the $32$-bit
117119
controller of the `xtensa_esp32_s3` board results in
118-
a runtime of $9.1~\text{ms}$ for the calculation.
120+
a runtime of $9.1~{\text{ms}}$ for the calculation.
119121

120122
Using only one core (core1) on the $32$-bit ARM(R) Cortex(R) M0+
121123
controller of the `rpi_pico_rp2040` board results in a calculation
122-
time of $19~\text{ms.}~$
124+
time of $19~{\text{ms}}$.
123125
The next generation `rpi_pico2_rp2350`
124126
with dual ARM(R) Cortex(R) M33 cores definitively improves on this
125-
(still using only core1) with a time of $6.3~\text{ms.}~$
126-
This is slightly more than $3~\text{ms}$ times faster
127-
than its predecessor.
127+
(still using only core1). It has a calculation time of $6.3~{\text{ms}}$,
128+
which is slightly more than $3$ times faster than its predecessor.

0 commit comments

Comments
 (0)