Dear Markus, The gcc benchmark (from SPEC CPU 2006, not 2017) took almost 9,000x to run on gem5 than on a beremetal machine when I measured how much slowdown they experience couple of years ago.
We used O3 CPU and the DRAMCtrl memory mode. If you are interested in the other benchmark results and detailed experimental settings, please see Fig. 3 of this paper. Soramichi Akiyama: "A Lightweight Method to Evaluate Effect of Approximate Memory with Hardware Performance Monitors", IEICE Transactions on Information and Systems, Vol. E102-D, No. 12, pp. 2354 - 2365, 2019. https://www.jstage.jst.go.jp/article/transinf/E102.D/12/E102.D_2019PAP0012/_pdf/-char/en Best regards, Soramichi Akiyama <s-a...@fc.ritsumei.ac.jp> Associate Professor, College of Information Science and Engineering, Ritsumeikan University, Japan On 2022/11/09 3:15, Markus Bichl via gem5-users wrote:
Dear gem5 users, I’m currently running SPEC CPU 2017 benchmarks. I was succesful creating a SPEC CPU 2017 disk image from this tutorial: https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/ <https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/> I used this image to start 3 benchmark runs on 3 different systems (server instance, desktop computer, and my laptop) 2 days ago. All of the systems have Intel Core/Xeon CPUs (but 5-7 years old), and 16 GBytes of DDR4 RAM. At this time, CPU load is 100% on one core for each system, at least 5 Gbytes of free memory. I started benchmarks using these commands: ./build/X86/gem5.fast ./configs/example/gem5_library/x86-spec-cpu2017-benchmarks.py --image /home//Projects/spec-2017/spec-2017-image/spec-2017 --partition 1 --benchmark 625.x264_s --size ref ./build/X86/gem5.fast ./configs/example/gem5_library/x86-spec-cpu2017-benchmarks.py --image /home//Projects/spec-2017/spec-2017-image/spec-2017 --partition 1 --benchmark 600.perlbench_s --size ref ./build/X86/gem5.fast ./configs/example/gem5_library/x86-spec-cpu2017-benchmarks.py --image /home//Projects/spec-2017/spec-2017-image/spec-2017 --partition 1 --benchmark 502.gcc_r --size test I wanted to have the results as fast as possible, so I used gem5.fast, and also tried the gcc benchmark with the test workload. As I do not see any progess on the benchmarks yet, I feel there is something wrong. Is this a normal simulation time for SPEC CPU 2017 benchmarks? Is it possible to track the progress of the simulations, even with "m5.disableAllListeners()” enabled in the system configuration? A run of 600.perlbench_s using the ref workload directly on the host system (server instance) took 181 seconds. Thanks a lot for your help! BR, Markus Bichl Student, Technische Universität Wien _______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
