2000
DOI: 10.1177/109434200001400306
|View full text |Cite
|
Sign up to set email alerts
|

Pace—A Toolset for the Performance Prediction of Parallel and Distributed Systems

Abstract: This paper describes a methodology that provides detailed predictive performance information throughout the software design and implementation cycles. It is structured around a hierarchy of performance models that describe the computing system in terms of its software, parallelization, and hardware components. The methodology is illustrated with an implementation, the performance analysis and characterization environment (PACE) system, which provides information concerning execution time, scalability, and reso… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
92
0
1

Year Published

2005
2005
2016
2016

Publication Types

Select...
9

Relationship

1
8

Authors

Journals

citations
Cited by 179 publications
(93 citation statements)
references
References 14 publications
0
92
0
1
Order By: Relevance
“…• Code analysis (Nudd et al, 2000;Reistad and Gifford, 1994) • Analytic benchmarking/code profiling (Yang et al, 1993) • Historical/Statistical prediction (Sanjay and Vadhiyar, 2008;Iverson et al, 1996) • Empirical analysis (Berman et al, 2005) Using these solutions, or by executing part of the code, other information related to user jobs can be obtained. In addition, there exists many studies which proposed models to estimate specific parameters (e.g., Cycle Per Instruction (CPI) (Chen and John, 2011;Intel Corporation, 2008), Memory Access Per Instruction (MPI) (Zhang and Chang, 2014) and estimated bandwidth (Zhu et al, 2012).…”
Section: Profiling and Prediction Phasementioning
confidence: 99%
“…• Code analysis (Nudd et al, 2000;Reistad and Gifford, 1994) • Analytic benchmarking/code profiling (Yang et al, 1993) • Historical/Statistical prediction (Sanjay and Vadhiyar, 2008;Iverson et al, 1996) • Empirical analysis (Berman et al, 2005) Using these solutions, or by executing part of the code, other information related to user jobs can be obtained. In addition, there exists many studies which proposed models to estimate specific parameters (e.g., Cycle Per Instruction (CPI) (Chen and John, 2011;Intel Corporation, 2008), Memory Access Per Instruction (MPI) (Zhang and Chang, 2014) and estimated bandwidth (Zhu et al, 2012).…”
Section: Profiling and Prediction Phasementioning
confidence: 99%
“…In the analytical modeling approach [31][36] [93], a scheduler predicts the performance of tasks in workflow on a given set of resources based on an analytic metric. For example, within GrADS [31], two types of performance models are developed, namely memory hierarchy performance model and computational model.…”
Section: Performance Estimationmentioning
confidence: 99%
“…ARMS has integrated Titan [111], which utilizes performance data obtained from PACE [93], a toolset for resource performance and usage analysis, with iterative heuristic algorithms to minimize the makespan and idle time of a grid resource. PACE can exact control flow, and use an analytical model approach based on queuing theory, to predict application performance on a given set of resources such as time, scalability and system resource usage.…”
Section: Gridflowmentioning
confidence: 99%
“…Wisconsin Wind Tunnel [19], PRO-TEUS [3] and the PACE toolkit [7,12] ) were originally envisaged as a mechanism to lower the burden of performance modelling by eliminating the need to manually inspect application source code. The automated replay of applications either in source or binary form allowed developers and performance modellers alike to experiment with performance by making direct changes to the application and simulating execution without requiring direct access to the specific machine in question.…”
Section: Performance Modellingmentioning
confidence: 99%