Difference between revisions of "Benchmarking: CPUBurn-in"
Jump to navigation
Jump to search
(Created page with "== Download CPUBurn-in == CPUBurn-in files can be obtained from: <code>//storage1/software/hpc/benchmarks/cpuburn-in/cpuburn-in.tar.gz</code> == Extract CPUBurn-in == <bash...") |
|||
| Line 14: | Line 14: | ||
== Run CPUBurn-in == | == Run CPUBurn-in == | ||
| − | It may be necessary to <code>chmod</code> the extracted binary to run (or execute the binary with <code>sh</code>: | + | It may be necessary to <code>chmod</code> the extracted binary to run (or execute the binary with <code>sh</code>): |
<syntaxhighlight> | <syntaxhighlight> | ||
[root@raldisk ~]# chmod +x cpuburn-in | [root@raldisk ~]# chmod +x cpuburn-in | ||
Revision as of 09:45, 17 September 2012
Download CPUBurn-in
CPUBurn-in files can be obtained from:
//storage1/software/hpc/benchmarks/cpuburn-in/cpuburn-in.tar.gz
Extract CPUBurn-in
[root@raldisk ~]# tar zxvf cpuburn-in.tar.gz
cpuburn-in
READMERun CPUBurn-in
It may be necessary to chmod the extracted binary to run (or execute the binary with sh):
[root@raldisk ~]# chmod +x cpuburn-inNote: cpuburn-in should have one running instance per core/virtual core. To achieve this, create a script to calculate the number of available core and run cpuburn-in a sufficient number of times to fully stress the cpus:
START=1
END=`cat /proc/cpuinfo | grep processor | wc -l`
for (( c=$START; c<=$END; c++ ))
do
nohup ./cpuburn-in 3600 &
done
topNB - the "3600" above is the number of seconds for the stress test to run.