*From: *Jason Lowe-Power via gem5-users
> *Date: *Tuesday, November 8, 2022 at 11:05 AM
> *To: *The gem5 Users mailing list
> *Cc: *Markus Bichl , Jason Lowe-Power <
> ja...@lowepower.com>
> *Subject: *[gem5-users] Re: SPEC CPU 2017 taking days to simulate
>
> Hi Markus, I
at 3:49 PM
To: gem5-users@gem5.org
Cc: Markus Bichl
Subject: [gem5-users] Re: SPEC CPU 2017 taking days to simulate
Hi Jason, hi Jonathan, thanks a lot for pointing out SimPoint! I’m currently
searching for details on how to use SimPoint with gem5. Is it right that I need
to run the benchmarks
1625...@student.tuwien.ac.at>>, Jason Lowe-Power
> mailto:ja...@lowepower.com>>
> Subject: [gem5-users] Re: SPEC CPU 2017 taking days to simulate
>
> Hi Markus, I would expect gem5 to be at least 10,000-100,000x slower than
> your host. So, if it takes 100 seconds on the ho
* 2022年11月9日 3:02
> *收件人:* The gem5 Users mailing list
> *抄送:* Markus Bichl ; Jason Lowe-Power <
> ja...@lowepower.com>
> *主题:* [gem5-users] Re: SPEC CPU 2017 taking days to simulate
>
>
>
> Hi Markus,
>
>
>
> I would expect gem5 to be at least 10,000-100,000x sl
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
Hi Markus,
I would expect gem5 to be at least 10,000-100,000x slower than your host.
So, if it takes 100 seconds on the host, then I would
expect between 1,000,000 and 10,000,000 seconds or more!
That's 277-2770 hours or 10-100 days!!
BTW, I actually think a 10-100,000x slowdown is on the low si
