SPEC CPU2006 benchmark descriptions

By John L. Henning. CARN, 2006

2,059 citations recorded by the source corpus.

Subfields: Computer Networks and Communications

View Paper: https://www.semanticscholar.org/paper/3e74ae88cdaa33bf89136800258bde97ab397ec9

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

Citations in the corpus

Context-Sensitive Fencing: Securing Speculative Execution via Microcode Customization (2019, methodology): “To this end, we include four benchmarks, bzip2, gcc, sjeng, omnet, from the SPEC CPU2006 suite [39] that exhibit varying degrees of instructionlevel parallelism.”
Practical Control Flow Integrity and Randomization for Binary Executables (2013, methodology): “We test CCFIR with the SPEC CPU2000 (consisting of SPECint2000 and SPECfp2000) benchmark binaries [43], SPECint2006 [44] and several COTS binaries including Firefox 3.6 (denoted as FF3) and Internet Explorer 6 (denoted as IE6)3 , to evaluate its overhead and protection.”
InvisiSpec: Making Speculative Execution Invisible in the Cache Hierarchy (2018, methodology): “We run individual SPECInt2006 and SPECFP2006 applications [34] on a single core, and multi-threaded PARSEC applications [35] on 8 cores.”
SoftSKU: Optimizing Server Architectures for Microservice Diversity @Scale (2019, result): “Relative to alternative benchmarks, our microservices exhibit (1) a greater IPC diversity than Google’s services [1] and (2) a lower IPC than most widely-studied SPEC CPU2006 benchmarks.”
Evaluating STT-RAM as an energy-efficient main memory alternative (2013, methodology): “We used a representative subset of applications from the SPEC CPU2006 suite [21] in our evaluations (14 total, 8 integer, 6 floating point).”
Eliminating the hypervisor attack surface for a more secure cloud (2011, background): “Approaches that add extra software to verify the integrity of the hypervisor, e.g., [9], add overhead, leave a small window open between the attack and the reactive defense, and do not protect against attacks that exploit bugs in the hypervisor for purposes other than injecting code or…”
CATalyst: Defeating last-level cache side channel attacks in cloud computing (2016, methodology): “tions We measure the impact on legacy applications using 22 SPEC CPU2006 [17] and 12 PARSEC [8] benchmarks.”
The gem5 Simulator: Version 20.0+ (2020, methodology): “2.9.4 DRAMPower and DRAM Power-Down Modes 35 .”
MemGuard: Memory bandwidth reservation system for efficient performance isolation in multi-core platforms (2013, methodology): “…reservation technique; (2) designing and implementing (in Linux kernel) an efficient memory bandwidth reservation system, named MemGuard; (3) evaluating MemGuard with an extensive set of realistic SPEC2006 benchmarks [11] and showing its effectiveness on a real multi-core hardware platform.”
Basic Performance Measurements of the Intel Optane DC Persistent Memory Module (2019, methodology): “These tests include three standardized benchmark suites: SPEC CPU 2006 [18], SPEC CPU 2017 [3], and PARSEC [40].”
Estimation of energy consumption in machine learning (2019, methodology): “They validate their models using empirical measurements of the SPECcpu2006 benchmarks [36].”
Benchmarking TPU, GPU, and CPU Platforms for Deep Learning (2019, background): “Indeed, benchmarks have been the driving force for compiler and architecture design for decades, and notable examples include the SPEC CPU [25] and PARSEC multiprocessor benchmarks [7].”
Accelerometer: Understanding Acceleration Opportunities for Data Center Overheads at Hyperscale (2020, background): “We frst present key leaf function breakdowns for our microservices and compare them with SPEC CPU2006 [54] and Google services [25, 63].”
SGXBOUNDS: Memory Safety for Shielded Execution (2017, background): “0 [25], as well singlethreaded SPEC CPU2006 [43].”