| While Gems can be slow, it isn't quite that slow. Of course, a lot depends on how many processors you have configured. Also, make sure you aren't compiling gems with debug flags turned on (that will slow down execution quite a bit). In general, I've found that it takes ~1 day on a 2.4GHz core 2 system to simulate a single core processor for 2 billion cycles. In general, runtimes will scale with the number of processors you're simulating, so a 2 processor simulation will take twice as long.
Phil On Jul 13, 2008, at 12:25 PM, Berkin Ozisikyilmaz wrote: I am not sure about the exact numbers but I think about 50 million instructions takes 12-16 hours to simulate so 10 billion instructions will not finish. Start small try 500K and then increase. berkin 'opal0.sim-step X' runs the simulation for X instructions. You need not use 'c' at all. I use your method to simulate it,But I type the command as below: simics>opal0.sim-step 9999999999 It will spend a long time to finish it,does it tell the simics doesn't stop until executing 9999999999 instructions? Is your meaning that after I use opal0.sim-step,wait it finish,then I use c to start simulate? then I can get the result?
_______________________________________________ Gems-users mailing list Gems-users@xxxxxxxxxxxhttps://lists.cs.wisc.edu/mailman/listinfo/gems-usersUse Google to search the GEMS Users mailing list by adding "site: https://lists.cs.wisc.edu/archive/gems-users/" to your search.
|
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}