Documentation for running spec cpu2006 benchmark #156
Comments
|
Thanks for bringing this up. The short is you need to;
The key file that does the automation is https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/perfkitbenchmarker/benchmarks/speccpu2006_benchmark.py I'll leave this bug open to create better directions but I wanted to try and unblock you. |
|
@voellm Could you provide the config file(linus64-x64-gcc47.cfg) that the benchmark should be run with? |
|
Alex, Did we get this to you? If not I can share it today. Tony On Mon, Apr 6, 2015 at 3:53 AM, Alex Krzos notifications@github.com wrote:
Anthony F. Voellm (aka Tony) |
|
@voellm I have not seen the config file yet, can it be posted on github? |
|
Nothing special here ... mostly you can see the patch level + the updated This is a sample config file for CPU2006. It was tested with:Compiler name/version: [gcc, g++, gfortran 4.7.2]Operating system version: [Debian 7, 64-bit]Hardware: [Core i7]If your platform uses different versions, differenthardware or operates in a different mode (forexample, 32- vs. 64-bit mode), there is the possibiliythat this configuration file may not work as-is.Note that issues with compilation should be directedto the compiler vendor. Information about SPEC techncialsupport can be found in the techsupport document in theDocs directory of your benchmark installation.Also note that this is a sample configuration. Itis expected to work for the environment in whichit was tested; it is not guaranteed that this isthe config file that will provide the best performance.Note that you might find a more recent config file foryour platform with the posted results atwww.spec.org/cpu2006#################################################################### AMD64 (64-bit) gcc 4.1.2 config fileSample Config file for CPU2006##################################################################### ignore_errors = yes default=default=default=default: Compiler selection##################################################################### HW configdefault sysinfo is expected to write hw_cpu_name, hw_memory, hw_nchips,hw_diskhw_model = System Model Name SW configdefault sysinfo is expected to write prepared_by, sw_os, sw_file, sw_statesw_compiler = gcc, g++ & gfortran 4.1.2 ##################################################################### Notes##################################################################### notes_os_000 ='ulimit -s unlimited' was used to set environment stack size ##################################################################### Optimization##################################################################### default=base=default=default: ##################################################################### 32/64 bit Portability Flags - all##################################################################### default=base=default=default: ##################################################################### Portability Flags##################################################################### 400.perlbench=default=default=default: 462.libquantum=default=default=default: 483.xalancbmk=default=default=default: 481.wrf=default=default=default: MD5 Last updated Tue Jul 22 17:52:14 2014optmd5=9cfdf297befcb821522c47564490dd33 401.bzip2=base=gcc47-64bit=default: Last updated Tue Jul 22 17:52:17 2014optmd5=5cdf34d9ef2b84066c8b64b47e8f6cc2 403.gcc=base=gcc47-64bit=default: Last updated Tue Jul 22 17:53:25 2014optmd5=baa7edd891f1086d96ce9a12f54abb6f 429.mcf=base=gcc47-64bit=default: Last updated Tue Jul 22 17:53:26 2014optmd5=985ccef82e533311c8a051b224a35041 445.gobmk=base=gcc47-64bit=default: Last updated Tue Jul 22 17:53:47 2014optmd5=25e22ffc983b480fbc8951f4c3b2bda0 456.hmmer=base=gcc47-64bit=default: Last updated Tue Jul 22 17:53:55 2014optmd5=af3d974d6c6fa5808621c70d5d4e9a13 458.sjeng=base=gcc47-64bit=default: Last updated Tue Jul 22 17:53:59 2014optmd5=5cdf34d9ef2b84066c8b64b47e8f6cc2 462.libquantum=base=gcc47-64bit=default: Last updated Tue Jul 22 17:54:01 2014optmd5=e8fa323a2475a196401d09c45150a5d0 464.h264ref=base=gcc47-64bit=default: Last updated Tue Jul 22 17:54:15 2014optmd5=af3d974d6c6fa5808621c70d5d4e9a13 471.omnetpp=base=gcc47-64bit=default: Last updated Tue Jul 22 17:54:43 2014optmd5=8a71b5dcff1be9fcb5ab9a4c0d47b7c2 473.astar=base=gcc47-64bit=default: Last updated Tue Jul 22 17:54:45 2014optmd5=486f7c5807dbc6270936d2896926dd70 483.xalancbmk=base=gcc47-64bit=default: Last updated Tue Jul 22 17:57:53 2014optmd5=a54152c5134d9a37014cf7b19ea7a56c 999.specrand=base=gcc47-64bit=default: Last updated Tue Jul 22 17:57:54 2014optmd5=5cdf34d9ef2b84066c8b64b47e8f6cc2 On Mon, Apr 27, 2015 at 7:06 AM, Alex Krzos notifications@github.com
Anthony F. Voellm (aka Tony) |
|
I think there's a typo in the config name above, it should be "linux64-x64-gcc47.cfg". There are a lot of examples of config files under your cpu2006-1.2/config directory. |
|
Yes you should be able to copy and paste. At some point make we should have
|
|
@voellm what do you think about add this config to perfkit data and upload it to VM by benchmark automaticaly? |
|
It's been a while, but #944 adds support for running the benchmark with just the iso file and a config file, rather than having to generate the tar file yourself (but a self-packaged tar file is still supported). The information about SPEC in the README has been updated accordingly: https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/README.md#licensing |
|
I used the config provided by @voellm ，but got errors as below when I running with fp, can you give some advice about this error, @voellm ############################################################################## INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN -- INVALID RUN'reportable' flag not set during run416.gamess (base) had invalid runs!481.wrf (base) had invalid runs!Run of 416.gamess (base) was not valid; status is VERun of 481.wrf (base) was not valid; status is REUnknown flags were used! Seehttp://www.spec.org/cpu2006/Docs/runspec.html#flagsurlfor information about how to get rid of this error.Error 416.gamess: Output miscompareError 416.gamess: Output miscompareError 416.gamess: Output miscompareError 481.wrf: copy 0 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 6 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 4 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 7 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 5 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 2 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 1 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 3 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 0 non-zero return code (exit code=2, signal=0)Error 481.wrf: copy 1 non-zero return code (exit code=2, signal=0) |
… config file provided by #156) - Add a flag allowing change build tool version - Make lint happy. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=177388988
|
C:\cpu2006\config>runspec --size=ref --iterations=1 --loose --tune=base --config=consolidateda 400.perlbench The log for this run is in C:\cpu2006/result/CPU2006.003.log
runspec finished at Tue Apr 3 10:06:12 2018; 29 total seconds elapsed C:\cpu2006\config> |
Is there any other documentation on running the SpecCPU2006 benchmark. Is the tarball generated from installing SpecCPU2006 from ISO on an image and then creating a new tarball from the directory? Can I run this benchmark if I only have the Spec ISO? I do not see my instances attempting to run install.sh nor do I see it referenced in the dev/master branch for the benchmark.
The text was updated successfully, but these errors were encountered: