derek/TheBandwidthBenchmark
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Jan Eitzinger
2021-09-28 12:51:57 +02:00
committed by GitHub
parent cd67a4cdf9
commit 91896f1cc0
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -11,7 +11,7 @@ It contains C modules for:
Moreover the benchmark showcases a simple generic Makefile that can be used in other projects. Moreover the benchmark showcases a simple generic Makefile that can be used in other projects.
You may want to have a look at our [[wiki|https://github.com/RRZE-HPC/TheBandwidthBenchmark/wiki]] for a collection of results that were created using TheBandwidthBenchmark. You may want to have a look at https://github.com/RRZE-HPC/TheBandwidthBenchmark/wiki for a collection of results that were created using TheBandwidthBenchmark.
## Overview ## Overview
@@ -124,7 +124,7 @@ Solution Validates
Apart from the highest sustained memory bandwidth also the scaling behavior within memory domains is a important system property. Apart from the highest sustained memory bandwidth also the scaling behavior within memory domains is a important system property.
There is a helper script included in util (```extractResults.pl```) that creates a text result file from multiple runs that can be used as input to plotting applications as gnuplot and xmgrace. There is a helper script downloadable at https://github.com/RRZE-HPC/TheBandwidthBenchmark/wiki/util/extractResults.pl that creates a text result file from multiple runs that can be used as input to plotting applications as gnuplot and xmgrace.
This involves two steps: Executing the benchmark runs and creating the data file. This involves two steps: Executing the benchmark runs and creating the data file.
To run the benchmark for different thread counts within a memory domain execute (this assumes bash or zsh): To run the benchmark for different thread counts within a memory domain execute (this assumes bash or zsh):