Memory referencing behavior in compiler-parallelized applications

Evan Torrie, Margaret Rose Martonosi, Mary W. Hall

Research output: Contribution to journalArticle

1 Scopus citations

Abstract

Compiler-parallelized applications are increasing in importance as moderatescale multiprocessors become common. This paper evaluates how features of advanced memory systems (e.g., longer cache lines) impact memory system behavior for applications amenable to compiler parallelization. Using full-sized input data sets and applications taken from the SPEC, NAS, PERFECT, and RICEPS benchmark suites, we measure statistics such as speedups, memory costs, causes of cache misses, cache line utilization, and data traffic. This exploration allows us to draw several conclusions. First, we find that larger granularity parallelism often correlates with good memory system behavior, good overall performance, and high speedup in these applications. Second, we show that when long (512 byte) cache lines are used, many of these applications suffer from false sharing and low cache line utilization. Third, we identify some of the common artifacts in compiler-parallelized codes that can lead to false sharing or other types of poor memory system performance, and we suggest methods for improving them. Overall, this study offers both an important snapshot of the behavior of applications compiled by state-of-the-art compilers, as well as an increased understanding of the interplay between cache line size, program granularity, and memory performance in moderate-scale multiprocessors.

Original languageEnglish (US)
Pages (from-to)349-376
Number of pages28
JournalInternational Journal of Parallel Programming
Volume24
Issue number4
DOIs
StatePublished - Jan 1 1996
Externally publishedYes

All Science Journal Classification (ASJC) codes

  • Software
  • Theoretical Computer Science
  • Information Systems

Fingerprint Dive into the research topics of 'Memory referencing behavior in compiler-parallelized applications'. Together they form a unique fingerprint.

  • Cite this