1. The simulation is very very slow and it seems
impossible to run the entire benchmark. 10 million cycles cost me more than one
hour. Although I can specify warm up length, it is best to cover the entire life
span of the benchmark. Has anyone tried to use a sampling approach? I guess
it's OK to wait on the completion of the entire benchmark when producing final
performance numbers, but it certainly is a pain whenever there is
modification to the code and we want to see how it affects the performance.
GEMS users, how do you handle this problem?