ACM Home Page
Please provide us with feedback. Feedback
FLASH vs. (simulated) FLASH: closing the simulation loop
Full text PdfPdf (268 KB)
Source ACM SIGPLAN Notices archive
Volume 35 ,  Issue 11  (November 2000) table of contents
Pages: 49 - 58  
Year of Publication: 2000
ISSN:0362-1340
Authors
Jeff Gibson  Computer Systems Lab, Stanford University, Stanford, CA
Robert Kunz  Computer Systems Lab, Stanford University, Stanford, CA
David Ofelt  Computer Systems Lab, Stanford University, Stanford, CA
Mark Horowitz  Computer Systems Lab, Stanford University, Stanford, CA
John Hennessy  Computer Systems Lab, Stanford University, Stanford, CA
Mark Heinrich  Computer Systems Lab, School of Electrical & Computer Engineering, Cornell University, Ithaca, NY
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 29,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/356989.356994
What is a DOI?

ABSTRACT

Simulation is the primary method for evaluating computer systems during all phases of the design process. One significant problem with simulation is that it rarely models the system exactly, and quantifying the resulting simulator error can be difficult. More importantly, architects often assume without proof that although their simulator may make inaccurate absolute performance predictions, it will still accurately predict architectural trends.This paper studies the source and magnitude of error in a range of architectural simulators by comparing the simulated execution time of several applications and microbenchmarks to their execution time on the actual hardware being modeled. The existence of a hardware gold standard allows us to find, quantify, and fix simulator inaccuracies. We then use the simulators to predict architectural trends and analyze the sensitivity of the results to the simulator configuration. We find that most of our simulators predict trends accurately, as long as they model all of the important performance effects for the application in question. Unfortunately, it is difficult to know what these effects are without having a hardware reference, as they can be quite subtle. This calls into question the value, for architectural studies, of highly detailed simulators whose characteristics are not carefully validated against a real hardware design.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
M. Durbhakula, V. Pai, and S. Adve. Improving the Speed vs. Accuracy Tradeoff for Simulating Shared-Memory Multiprocessors with ILP Processors. Rice University ECE Technical Report 9802, June 1998.
 
4
 
5
6
 
7
M. Heinrich, D. Ofelt, M. Horowitz, and J. Hennessy. Hardware/Software Codesign of the Stanford FLASH Multiprocessor. In Proceedings of the IEEE Special Issue on Hardware/Software Co-design, 85(3), March 1997.
8
9
 
10
P.S. Magnusson, F. Dahlgren, H. Grahn, et al. SimICS/sun4m: A VirtualWorstation. In Proceedings of the Usenix Annual Technical Conference, June 1998.
 
11
12
 
13
L. McVoy and C. Staelin. lmbench: Portable tools for performance analysis. USENIX technical conference, pages 279-284, January 1996.
 
14
V. S. Pai, P. Ranganathan, and S. V. Adve. RSIM Reference Manual version 1.0. Technical Report #9705, Department of Electrical and Computer Engineering, Rice University, August 1997.
 
15
 
16
U. Prestor. Snbench homepage, on-line at http://www.cs.utah.edu/~uros/snbench.
17
 
18
M. Rosenblum. Personal Communication.
 
19
 
20
Standard Performance Evaluation Corporation. The SPEC95 Benchmark Suite. Details on-line at http://www.specbench.org/.
 
21
Stanford Parallel Applications for Shared Memory. SPLASH-2 web page, on-line at http://www-flash.stanford.edu/apps/SPLASH.
 
22
23
 
24
25
 
26
Kenneth Yeager. Personal Communication.
 
27

Collaborative Colleagues:
Jeff Gibson: colleagues
Robert Kunz: colleagues
David Ofelt: colleagues
Mark Horowitz: colleagues
John Hennessy: colleagues
Mark Heinrich: colleagues