1995
DOI: 10.1109/71.466630
|View full text |Cite
|
Sign up to set email alerts
|

A trace-driven simulator for performance evaluation of cache-based multiprocessor systems

Abstract: We describe a simulator which emulates the activity of a shared memory, common bus multiprocessor system with private caches. Both kernel and user program activities are considered, thus allowing an accurate analysis and evaluation of coherence protocol performance. The simulator can generate synthetic traces, based on a wide set of input parameters which specify processor, kernel and workload features. Other parameters allow us to detail the multiprocessor architecture for which the analysis has to be carried… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
28
0

Year Published

1997
1997
2010
2010

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 31 publications
(28 citation statements)
references
References 20 publications
0
28
0
Order By: Relevance
“…Trace Factory then models the execution of complex multiprogrammed workloads by combining multiple source traces and simulating system calls (which could also involve I/O activity), process scheduling and virtual-to-physical address translation. Finally, Trace Factory produces the references (target trace, Table 2) furnished as input to a memory-hierarchy simulator [31]. Trace Factory generates references according to an on-demand policy: it produces a new reference when simulator requests one, so that the timing behavior imposed by the memory subsystem conditions the reference production [17,18].…”
Section: Methodology and Workloadmentioning
confidence: 99%
See 3 more Smart Citations
“…Trace Factory then models the execution of complex multiprogrammed workloads by combining multiple source traces and simulating system calls (which could also involve I/O activity), process scheduling and virtual-to-physical address translation. Finally, Trace Factory produces the references (target trace, Table 2) furnished as input to a memory-hierarchy simulator [31]. Trace Factory generates references according to an on-demand policy: it produces a new reference when simulator requests one, so that the timing behavior imposed by the memory subsystem conditions the reference production [17,18].…”
Section: Methodology and Workloadmentioning
confidence: 99%
“…The methodology that we used is based on trace-driven simulation [19,31,36,47] and on the simulation of the three kernel activities that most affect performance: system calls, process scheduling, and virtual-to-physical address translation.…”
Section: Methodology and Workloadmentioning
confidence: 99%
See 2 more Smart Citations
“…The simulation methodology relies on trace-driven technique, by means of Trace Factory environment [8], [15].…”
Section: Introductionmentioning
confidence: 99%