Benchmarking: HEPSPEC
Copy over the files
- Note: Use SPEC2006_v12.tar.bz2
Copy over the spec2k6 files from the shared directory: //10.0.0.220/software/hpc/benchmarks/SPEC2006_v12.tar.bz2
NOTE Place all files in the same directory
32 bit libs
Make sure you have the 32bit libs installed!
# CentOS 6
yum groupinstall 'Development tools'
yum install glibc-devel-2.12-1.47.el6.i686 compat-gcc-34-g77
# CentOS 5
yum groupinstall 'Development tools'
yum install glibc-devel compat-gcc-34-g77
## JH Test
yum install glibc-devel.i686 libstdc++.i686 sharutils gcc-c++
yum install compat-libstdc++-33.i686 libstdc++-devel.i686 compat-libcap1.i686Download the CERN HEPSPEC configuration file
# check https://twiki.cern.ch/twiki/bin/view/FIOgroup/TsiBenchHEPSPEC for the latest version
# OLD: wget --no-check-certificate https://twiki.cern.ch/twiki/pub/FIOgroup/TsiBenchHEPSPEC/spec2k6-2.14.tar.gz
wget --no-check-certificate https://twiki.cern.ch/twiki/pub/FIOgroup/TsiBenchHEPSPEC/spec2k6-2.23.tar.gzExtract the spec config files
NB: When running HEPSPEC for a CERN configuration with the default CERN filesystem layout, do not attempt to run HEPSPEC from within "/" or "/root/". The default partition size is not big enough, the partition will run out of space and the benchmark will fail. Use "/pool/" instead.
david@cal1:~/$ mkdir -p scratch/hepspec && cd scratch/hepspec
david@cal1:~/scratch/hepspec$ mv ~/spec2k6-2.14.tar.gz .
david@cal1:~/scratch/hepspec$ tar zxvf spec2k6-2.14.tar.gz
linux32-gcc_cern.cfg
linux64-gcc_cern.cfg
README.TXT
runspec.sh
simple.shEdit the runspec.sh file
NOTE 1 Make sure this is done or results get sent to cern (if email is configured on the server)
NOTE 2 The RESULTDIR variable must point to a directory that exists (the script won't create it). If it doesn't exist, the results won't be saved!
# vi runspec.sh
EMAIL="hpc@boston.co.uk"
RESULTDIR="/home/david/scratch/hepspec/results-spec"Run HEPSPEC
# as root
./runspec.sh -d "Benchmark HEPSPEC2006 32bit" -a 32 -b all_cppNOTE Extracting the tar.bz2 files takes some time. If the build fails after the archive is extracted, remove the following line from runspec (around line 75) and rerun the build
tar xjf $SPECTARBALL || fail "Unable to extract SPECint!"Results
Intel Results
| CPU | Freq | Cores | Hepspec (no HT) | Hepspec (with HT) |
|---|---|---|---|---|
| Sandy Bridge | ||||
| E5-2687W | 3.10GHz | 8 | 346.97 | 419 |
| E5-2690 | 2.90GHz | 8 | 324.58 | 392 |
| E5-2680 | 2.70GHz | 8 | 291.13 | 352 |
| E5-2670 | 2.60GHz | 8 | 246.20 | 346 |
| E5-2665 | 2.40GHz | 8 | 268.62 | 320.86 |
| E5-2660 | 2.20GHz | 8 | 246.24 | 297 |
| E5-2650 | 2.00GHz | 8 | 223.85 | 270 |
| E5-2650L | 1.80GHz | 8 | 239.17 | |
| E5-2640 | 2.50GHz | 6 | 196.39 | 237 |
| E5-2630 | 2.30GHz | 6 | 180.68 | 218 |
| E5-2620 | 2.00GHz | 6 | 157.11 | 190 |
| Westmere/Nehalem | ||||
| X5680 | 3.33GHz | 6 | 204.03 | |
| X5670 | 2.93GHz | 6 | 181.15 | |
| X5660 | 2.80GHz | 6 | 173.2 | |
| X5650 | 2.66GHz | 6 | 164.46 | |
| E5640 | 2.66GHz | 4 | 102.35 | |
| E5630 | 2.53GHz | 4 | 97.35 | |
| E5620 | 2.40GHz | 4 | 92.35 | |
| Ivy Bridge | ||||
| E5-2650 V2 | 10 | 366.8 | ||
| E5-2660 V2 | 10 | 405.4 | ||
| E5-2690 V2 | 10 | 489.05 | ||
| Haswell | ||||
| E5-2695 V3 | 531.85 | |||
AMD Results
| CPU | Freq | CPU | Hepspec |
|---|---|---|---|
| Abu Dhabi | |||
| 6380 | x.xxGHz | xx | 286.4 |
| Interlagos | |||
| 6282 | x.xxGHz | xx | 308.82 |
| 6276 | x.xxGHz | xx | 288.90 |
| 6274 | x.xxGHz | xx | 268.98 |
| 6272 | x.xxGHz | xx | 259.01 |
| 6238 | x.xxGHz | xx | 179.32 |
| 6234 | x.xxGHz | xx | 171.85 |
| 6220 | x.xxGHz | xx | 109.58 |
| 6212 | x.xxGHz | xx | 99.62 |
| Magney-Cours | |||
| 6174 | 2.20GHz | 12 | 195.42 |
| 6172 | 2.10GHz | 12 | 186.54 |
| 6168 | 1.90GHz | 12 | 168.77 |
| 6136 | 2.40GHz | 8 | 142.12 |
| 6134 | 2.30GHz | 8 | 136.2 |
| 6128 | 2.00GHz | 8 | 118.44 |