I think the short answer is -- all the easy stuff has already been done. A lot of the if statements have branch predictor hints, debug output is cut down to a minimum when building without debug mode, etc.
Any real speedup would come from trying to parallelize the code, but I doubt that will happen any time soon (if ever) -- the simulator is just too detailed and complex to be easily parallelizable. So I think as a community, we just have to accept the fact that detailed simulation is slow. On Wed, Sep 7, 2011 at 4:54 PM, sparsh1 mittal1 <[email protected]>wrote: > Hello > Does anyone have suggestion regarding speeding-up marss ? I am sure, this > point will help others also. > > My friends who had used M5 told me, that in M5 the simulation speed reduces > almost linearly with number of cores. Given this, the speed of Marss with > multi-cores is already impressive! Yet, further speed-ups will help. > > Some general ideas are reducing print-outs, I/O. Yet, would you like to > share more specific and substantial speed-up ideas? For example, my main > interest is in cache related work. > > I would appreciate it. > > Thanks and Regards > Sparsh Mittal > > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
