Hi All, I am sorry to bother everyone. I am trying to gauge performance and would love some feedback on run-time performance. My main impetus for this Email is due to limited information I could find and just wanted to get some feedback on if there was some issues related to this topic. I apologize in advance if I missed something specific about this question.
I did some tests on the queens benchmark as well as some others and my run times seem to take a long time. 16X grids within queens.c (e.g., queens 16) seem to run about 17 hours using AtomicMemory access with caching. The ASPLOS-13 tutorial seems to have very small numCycles, so not sure that is accurate for “-o 16” on queens.c. Eventually, I would love SPEC, but I am quite worried if queens.c takes forever, how can I even manage to get SPEC through. I also tried some other benchmarks like Matrix Multiplications, but some of them take just as long. However, queens does take a while to run, which I know is typical due to its intense computation mix. My x86 cycle counts (statically compiled with -O3 and loop unrolling) were: 60,055,907,458 on multi-core Intel extreme processors - again, I might have not run something correctly. If anyone can possibly share their tips/tricks - especially for eventual running of SPEC, it would be great. Does anyone do anything to maximize performance? Even the smallest of tips would be helpful. Perhaps, I am running gem5 with the wrong settings. Or, perhaps, the settings are correct and this is a normal set of run times. Anyways, I appreciate any help and also appreciate the wonder of gem5. Take care. All my best, James _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
