PARSEC vs. SPLASH-2: A quantitative comparison of two multithreaded benchmark suites on chip-multiprocessors

Christian Bienia, Sanjeev Kumar, Kai Li

Research output: Chapter in Book/Report/Conference proceedingConference contribution

171 Scopus citations

Abstract

The PARSEC benchmark suite was recently released and has been adopted by a significant number of users within a short amount of time. This new collection of workloads is not yet fully understood by researchers. In this study we compare the SPLASH-2 and PARSEC benchmark suites with each other to gain insights into differences and similarities between the two program collections. We use standard statistical methods and machine learning to analyze the suites for redundancy and overlap on Chip-Multiprocessors (CMPs). Our analysis shows that PARSEC workloads are fundamentally different from SPLASH-2 benchmarks. The observed differences can be explained with two technology trends, the proliferation of CMPs and the accelerating growth of world data.

Original languageEnglish (US)
Title of host publication2008 IEEE International Symposium on Workload Characterization, IISWC'08
Pages47-56
Number of pages10
DOIs
StatePublished - 2008
Event2008 IEEE International Symposium on Workload Characterization, IISWC'08 - Seattle, WA, United States
Duration: Sep 14 2008Sep 16 2008

Publication series

Name2008 IEEE International Symposium on Workload Characterization, IISWC'08

Other

Other2008 IEEE International Symposium on Workload Characterization, IISWC'08
Country/TerritoryUnited States
CitySeattle, WA
Period9/14/089/16/08

All Science Journal Classification (ASJC) codes

  • Computer Science Applications
  • Hardware and Architecture
  • Control and Systems Engineering

Keywords

  • Benchmark suite
  • Multithreading
  • Performance measurement
  • Shared-memory computers

Fingerprint

Dive into the research topics of 'PARSEC vs. SPLASH-2: A quantitative comparison of two multithreaded benchmark suites on chip-multiprocessors'. Together they form a unique fingerprint.

Cite this