douzeb/sbc-performance-test-kit
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update README.md

Browse source
This commit is contained in:
Lab 8916100448256 2021-01-11 20:36:57 +00:00
parent bef3accb75
commit e45209133a
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -8,22 +8,23 @@ These benchmarking are done in the context of choosing a hardware platform for s
The testing procedure mainly focusses on energy consuption and CPU/memory/disk speed. The testing procedure mainly focusses on energy consuption and CPU/memory/disk speed.
The full test procedure during which the energy consumption is measured takes one hour. The full test procedure during which the energy consumption is measured takes one hour.
During that period the CPU is heavily stressed for around 40 minutes and is mostly idle during the remaining 20 minutes. During that period the CPU is heavily stressed for around 40 minutes, the system is idle for 10 minutes and the remaining 10 minutes are taken by the CPU/Memory/Disk tests (these tests can actually last less or more than 10 minutes depending on the performance of the machine being tested but the nergy consumption is done on the 60 first minutes after the styart of the test).
By default the disk speed is measured for sequential reads, sequential writes and a mix of random reads and writes with a 2 to 1 ratio (2 reads for 1 write) with a block size of 1024 KiB over 512 files of 128 MiB each (64 GiB total) By default the disk speed is measured for sequential reads, sequential writes and a mix of random reads and writes with a 2 to 1 ratio (2 reads for 1 write) with a block size of 1024 KiB over 512 files of 128 MiB each (64 GiB total)
But the total disk space that is used is adapted depending on the target board specs. The goal is to use a disk space that is at least 2 times larger than the system memory size to avoid having the results biased by the system file cache.
The total disk space used is adapted depending on the target board specs. The goal is to use a disk space that is at least 2 times as large as the system memory size to avoid having the results biased by the Linux file cache.
## Credits ## Credits
The performance measurements and system stressing are mainly done thanks to [sysbench](https://github.com/akopytov/sysbench) The performance measurements and system stressing are mainly done thanks to [sysbench](https://github.com/akopytov/sysbench)
[hdparm](https://sourceforge.net/projects/hdparm/) is also used to get disk information and to measure raw disk read speed [hdparm](https://sourceforge.net/projects/hdparm/) is also used to get disk information and to measure raw read disk speed
[lm_sensors](https://github.com/lm-sensors/lm-sensors) is used to measure CPU temperature [lm_sensors](https://github.com/lm-sensors/lm-sensors) is used to measure CPU temperature
System information is gathered with [smartctl](https://www.smartmontools.org/), though the Linux /proc filesystem or using some other small command line utilities like lsblk, uname, grep, cut, ... System information is gathered with [smartctl](https://www.smartmontools.org/), though the Linux /proc filesystem or using some other small command line utilities like lsblk, uname, grep, cut, ...
The script used to automate the tests is run with [bash](https://www.gnu.org/software/bash/) on [Debian GNU/Linux](https://www.debian.org/) or a derivative distribution.
## Testing procedure ## Testing procedure