Semiconductor & Computer Engineering
| Line 34: | Line 34: | ||
** '''Frequency:''' 296 MHz | ** '''Frequency:''' 296 MHz | ||
* '''Introduction:''' 1997 | * '''Introduction:''' 1997 | ||
| + | |||
| + | == Retirement == | ||
| + | SPEC stopped accepting official results for publications on December 26, 2017 3:01AM US Eastern Time. CPU2006 official retired on January 9, 2018 US Eastern Time end of day. No new publications are possible anymore. For new benchmarks results, see [[SPEC CPU2017]]. | ||
Latest revision as of 22:45, 27 January 2018
SPEC CPU2006 is an industry-standardized CPU benchmarking suite introduced by SPEC in 2006 as a replacement to the previous CPU2006 suite. CPU2006 was officially released on August 24, 2006.
Overview[edit]
Introduced in 2006, CPU2006 consists of 29 benchmarks organized into four categories:
| Integer | Floating Point | |
|---|---|---|
| Latency | SPECint2006 SPECint_base2006 | SPECfp2006 SPECfp_base2006 |
= time_on_reference_machine / time_on_SUT | ||
| Throughput | SPECint_rate2006 SPECint_rate_base2006 | SPECfp_rate2006 SPECfp_rate_base2006 |
= number_of_copies * (time_on_reference_machine / time_on_SUT) | ||
- Latency ("speed"; SPEC*2006) - The time it takes to run 1 task at a time. The shorter the time, the faster the execution and thus higher score.
- Throughput ("rate"; SPEC*_rate*2006) - The amount of work that can be done in a unit of time. The more work done at a given time the higher the throughput and thus higher score. The tester chooses how many tasks to run (ideally highest sustainable).
Regardless of the metric, higher performance yields higher score.
Compilation[edit]
Because the test suite must be compiled on the tester's machine, the way compilation is conducted becomes a point disputes (e.g., no optimization?, default optimization?, higher optimization?). CPU2006 defines two compilation possibilities:
- base metric (_base) - this metric is required for all reports. The base metric requires that all modules in the suite be compiled using the same flags and in the same order for each language.
- peak metric (no suffix) - this metric is optional. The peak metric provides flexibility for tests that want to extract additional performance through higher compiler optimization by using additional different compiler options.
Note that the base is a subset of the peak metric. That is, all base results are valid peak results, but not all peak results are valid base results.
Reference Machine[edit]
As mentioned above, the performance is normalized using a reference machine. The reference machine is:
- Vendor: Sun Microsystems
- Machine: Ultra Enterprise 2
- CPU: UltraSPARC II
- Frequency: 296 MHz
- Introduction: 1997
Retirement[edit]
SPEC stopped accepting official results for publications on December 26, 2017 3:01AM US Eastern Time. CPU2006 official retired on January 9, 2018 US Eastern Time end of day. No new publications are possible anymore. For new benchmarks results, see SPEC CPU2017.