(To check for possible updates to this document, please see http://www.spec.org/power_ssj2008/docs/SPECpower_ssj2008-Result_File_Fields.html)

Overview

Selecting one of the following will take you to the detailed table of contents for that section:

1. SPECpower_ssj2008 Benchmark

2. Main Report File

3. Top Bar

4. Benchmark Results Summary

5. System Under Test

6. System Under Test Notes

7. Controller System

8. Measurement Devices

9. Notes

10. Electrical and Environmental Data

11. Aggregate Performance Data

12. Aggregate Performance Report

13. JVM Instance Summary

14. JVM Instance Scores

15. JVM Instance Performance Report

16. Performance Details

Detailed Contents

1. SPECpower_ssj2008 Benchmark

1.1 The Workload

1.1.1 Server Side Java

1.1.2 JVM Director

1.2 The Control and Collect System

1.3 The Power and Temperature Daemon

1.4 Result Validation and Report Generation

1.5 References

2. Main Report File

3. Top bar

3.1 Headline

3.2 Test sponsor

3.3 SPEC license #

3.4 Hardware Availability

3.5 Tested by

3.6 Test Location

3.7 Software Availability

3.8 System Source

3.9 Test Date

3.10 Publication Date

3.11 INVALID

4. Benchmark Results Summary

4.1 Performance

4.1.1 Target Load

4.1.2 Actual Load

4.1.3 ssj_ops

4.1.4 Active Idle

4.2 Power

4.2.1 Average Power (W)

4.3 Performance to Power Ratio

4.4 ∑ssj_ops / ∑power =

4.5 Result Chart

5. System Under Test

5.1 Hardware

5.1.1 Hardware Vendor

5.1.2 Model

5.1.3 CPU Name

5.1.4 CPU Characteristics

5.1.5 CPU Frequency (MHz)

5.1.6 CPU(s) Enabled

5.1.7 Hardware Threads / Core

5.1.8 CPU(s) orderable

5.1.9 Primary Cache

5.1.10 Secondary Cache

5.1.11 Tertiary Cache

5.1.12 Other Cache

5.1.13 Memory Amount (GB)

5.1.14 # and size of DIMM(s)

5.1.15 Memory Details

5.1.16 Power Supply Quantity and Rating

5.1.17 Power Supply Details

5.1.18 Disk Drive

5.1.19 Disk Controller

5.1.20 # and type of Network Interface Cards (NICs) Installed

5.1.21 NICs Enabled in Firmware / OS / Connected

5.1.22 Network Speed

5.1.23 Keyboard

5.1.24 Mouse

5.1.25 Monitor

5.1.26 Optical Drives

5.1.27 Other Hardware

5.2 Software

5.2.1 Power Management

5.2.2 Operating System (OS)

5.2.3 OS Version

5.2.4 Filesystem

5.2.5 JVM Vendor

5.2.6 JVM Version

5.2.7 JVM Options

5.2.8 JVM Affinity

5.2.9 JVM Instances

5.2.10 JVM Initial Heap Memory (MB)

5.2.11 JVM Maximum Heap Memory (MB)

5.2.12 JVM Address Bits

5.2.13 Benchmark Version

5.2.14 Director Location

5.2.15 Other Software

6. System Under Test Notes

7. Controller System

7.1 Hardware

7.1.1 Hardware Vendor

7.1.2 Model

7.1.3 CPU Description

7.1.4 Memory amount (GB)

7.2 Software

7.2.1 Operating System (OS)

7.2.2 JVM Vendor

7.2.3 JVM Version

7.2.4 CCS Version

8. Measurement Devices

8.1 Power Analyzer

8.1.1 Hardware Vendor

8.1.2 Model

8.1.3 Serial Number

8.1.4 Connectivity

8.1.5 Current Range

8.1.6 Voltage Range

8.1.7 Input Connection

8.1.8 Calibration Institute

8.1.9 Accredited by

8.1.10 Calibration Label

8.1.11 Date of Calibration

8.1.12 PTDaemon Host System

8.1.13 PTDaemon Host OS

8.1.14 PTDaemon Version

8.2 Temperature Sensor

8.2.1 Hardware Vendor

8.2.2 Model

8.2.3 Driver Version

8.2.4 Connectivity

8.2.5 PTDaemon Host System

8.2.6 PTDaemon Host OS

9. Notes

10. Electrical and Environmental Data

10.1 Target Load

10.2 Electrical Data

10.2.1 Average Voltage (V)

10.2.2 Average Current (A)

10.2.3 Average Power Factor

10.2.4 Average Power (W)

10.2.5 Line Standard

10.2.6 Average Power Factor

10.3 Environmental Data

10.3.1 Minimum Ambient Temperature (°C)

10.3.2 Minimum Temperature (°C)

10.3.3 Elevation (m)

11. Aggregate Performance Data

11.0.1 Target Load

11.0.2 Actual Load

11.1 ssj_ops

11.1.1 Target

11.1.2 Actual

11.1.3 ssj_ops@calibrated=

11.2 ssj_ops Chart

12. Aggregate Performance Report

12.1 Top bar

12.2 Benchmark Results Summary

12.3 System Under Test

12.4 System Under Test Notes

12.5 Notes

13. JVM Instance Summary

13.0.1 JVM Instance

13.0.2 ssj_ops@100%

13.0.3 ssj_ops@100% per JVM

13.0.4 Aggr. JVM ssj_ops Chart

14. JVM Instance Scores

14.0.1 Target Load

14.0.2 Actual Load

14.1 ssj ops

14.1.1 Target

14.1.2 Actual

14.1.3 ssj_ops@calibrated=

14.2 ssj_ops Chart

15. JVM Instance Performance Report

15.1 Top bar

15.2 Benchmark Results Summary

15.3 System Under Test

15.4 System Under Test Notes

15.5 Notes

16. Performance Details

16.0.1 Target Load

16.0.2 Actual Load

16.0.3 Transaction Type

16.0.4 Count

16.0.5 Total Heap (MB)

1. SPECpower_ssj2008 Benchmark

SPECpower_ssj2008 is the first generation SPEC benchmark for evaluating the power and performance of server class computers.
The benchmark suite consists of three separate software modules:

• Workload (SSJ)
• Power and Temperature Daemon (PTD)
• Control and Collect System (CCS)

1.1 The Workload

1.1.1 Server Side Java Business Application Simulation

The workload is a Java program designed to exercise the CPU(s), caches, memory, the scalability of shared memory processors, JVM (Java Virtual Machine) implementations, JIT (Just In Time) compilers, garbage collection, threads, and certain aspects of the operating system of the SUT.
The workload architecture is a 3-tier system with emphasis on the middle tier. These tiers are comprised as follows:

1. Random input selection
2. Business logic (fully implemented by SPECpower_ssj2008)
3. Tables of objects, implemented by Java Collections (rather than a separate database)

1.1.2 JVM Director

The JVM Director is a separate and distinct mechanism from the actual workload itself (the three-tiered client-server environment), but runs concurrently with the JVM instance(s) of the workload. Like the workload, the JVM Director is also a java application, and as such, runs as its own JVM instance.
The JVM Director can be run locally on the SUT, or it can be run remotely at the user’s discretion (see Director Location). Whichever method is employed, the JVM Director and the workload JVM instance(s) will communicate via a TCP/IP socket connection.

1.2 The Control and Collect System

The Control and Collect System is a Java-based application that resides on the controller server. CCS is used to connect to three types of data sources via TCP/IP socket communication:

• the SSJ module (via the JVM Director) on the SUT
• an instance of PTD connected to a power analyzer
• an instance of PTD connected to a temperature sensor

1.3 The Power and Temperature Daemon

The Power and Temperature Daemon (PTD) is a single executable program that communicates with a power analyzer or a temperature sensor via the server’s native RS-232 or USB port. It reports the power consumption or temperature readings to CCS via a TCP/IP socket connection. It supports a variety of RS-232, GPIB and USB interface command sets for a variety of power analyzers and temperature sensors. PTD is the only of the three SPECpower_ssj2008 software modules that is not Java based. Although it can be quite easily setup and run on a server other than the controller server, in the simplest SPECpower_ssj2008 test bed implementation, the PTD will typically reside on the controller server.

1.4 Result Validation and Report Generation

At the beginning of each run, the benchmark parameters are checked for conformance to the run rules. Warnings are displayed for non-compliant properties and printed in the final report; however, the benchmark will run to completion producing a report that is not valid for publication.
At the end of a benchmark run the report generator module is called to generate the report files described here from the data given in the configuration files and colleted during this benchmark run. Again basic validity checks are performed, to ensure that interval length, target load throughput, temperature etc. are within the limits defined in the run rules. For more information see section "2.5.2 Validity Checks" in the Run and Reporting Rules document.

1.5 References

More detailed information can be found in the documents shown in the following table. For the latest versions, please consult SPEC’s website.

2. Main Report File

This section gives an overview of the information and result fields in the main report file. Additional information is shown in the Aggregate Performance Report, which adds performance data for each of the possibly used JVM instances. This information is further extended in the JVM Instance Performance Report which includes details about the different types of transactions performed during each measurement interval.

3. Top bar

The top bar shows the measured SPECpower_ssj2008 result and gives some general information regarding this test run.

3.1 Headline

The headline of the performance report includes one field displaying the hardware vendor (config.hw.vendor) and the name (config.hw.model) of the system under test. In a second field the overall SPECpower_ssj2008 result achieved in this test (overall ssj_ops/watt) is printed, eventually prefixed by an "Invalid" indicator, if the current result does not pass the validity checks implemented in the SPECpower_ssj report generation software. More detailed information about the result metric is presented in section 4.3.1 of the SPECpower_ssj2008 Run and Reporting Rules.

3.2 Test sponsor

The name of the organization or individual that sponsored the test. Generally, this is the name of the license holder (config.test.sponsor).

3.3 SPEC license #

The SPEC license number of the organization or individual that ran the result (config.test.spec_license).

3.4 Hardware Availability

The date when all the hardware necessary to run the result is generally available (config.hw.available). For example, if the CPU is available in Aug-2007, but the memory is not available until Oct-2007, then the hardware availability date is Oct-2007 (unless some other component pushes it out farther).

3.5 Tested by

The name of the organization or individual that ran the test and submitted the result (config.test.tested_by).

3.6 Test Location

The name of the city, the state and country the test took place. If there are installations in multiple geographic locations, that must also be listed in this field (config.test.location).

3.7 Software Availability

The date when all the software necessary to run the result is generally available (config.sw.available). For example, if the operating system is available in Aug-2007, but the JVM is not available until Oct-2007, then the software availability date is Oct-2007 (unless some other component pushes it out farther).

3.8 System Source

Single Supplier or Parts Built (config.hw.system_source)

• Single Supplier
  “Single Supplier” is defined as a SUT configuration where all hardware is provided by a single supplier.
• Parts Built
  “Parts Built” is defined as a SUT configuration where hardware is provided by multiple suppliers. A "Parts Built" system disclosure must include enough detail to procure and reproduce all aspects of the submission, including performance and power.

3.9 Test Date

The date when the test is run. This value is automatically supplied by the SPECpower_ssj software; the time reported by the system under test is recorded in the raw result file .

3.10 Publication Date

The date when this report will be published after finishing the review. This date is automatically filled in with the correct value by the submission tool provided by SPEC. By default this field is set to "Unpublished" by the software generating the report.

3.11 INVALID

Any inconsistencies with the run and reporting rules causing a failure of one of the validity checks implemented in the report generation software will be reported here and all pages of the report file will be stamped with an "Invalid" water mark in case this happens. The printed text will show more details about which of the run rules wasn't met and the reason why.

4 Performance Results Summary

This section describes the result details for all measurement intervals in a table and as a graph.

4.1 Performance

The first three columns of the results table show the measured throughput and the actual percentage of calibrated throughput compared to the target percentage.

4.1.1 Target Load

The different target load levels derived from the calibrated throughput, starting with 100% of the calibrated throughput and decreasing to "Active Idle" = 0% or no throughput. The benchmark software schedules the required number of requests to actually achieve the intended throughput levels during each of the measurement intervals, each lasting 240 seconds.

4.1.2 Actual Load

The load levels actually achieved during the different phases of the benchmark as a percentage of the calibrated throughput. The percentages must match the target load of each phase with less than 2% deviation (positive or negative).

4.1.3 ssj_ops

The number of operations finished during this measurement interval divided by the number of seconds defined for this interval, showing the throughput (workload operations per second) for this period.

4.1.4 Active Idle

The last measurement interval running without any transactions scheduled by the workload software. So there is no throughput reported for this interval only the power consumption will be measured and displayed.

4.2 Power

This column of the results summary table shows the power consumption for the different target loads.

4.2.1 Average Power (W)

Average power measured by the power analyzer and accumulated by the PTD (Power and Temperature Daemon) for this measurement interval, displayed as watts (W).

4.3 Performance to Power Ratio

The average throughput divided by the average power consumption for each of the measurement intervals.

4.4 ∑ssj_ops / ∑power =

4.5 Result Chart

The result chart graphically displays the results reported in the summary table in one diagram. The red bars show the performance (throughput) to power ratio of each target load given on the y-axis graphically (corresponding to the upper x-axis) and numerically as a label in the bar. Longer bars / higher numbers are better. By definition there is no throughput for the "Active Idle" level and so the ratio is always 0. The bold blue line with the markers corresponds to the lower x-axis and shows the average power consumption for each target load given on the y-axis. Lower numbers are better. The thin, vertical, straight line corresponds to the upper x-axis and shows the overall ssj_ops per watt result of the benchmark. A higher number is better.

5. System under test

The following section of the report file describes the hardware and the software of the system under test (SUT) used to run the reported SPECpower benchmark with the level of detail required to reproduce this result.

5.1 Hardware

This section describes in detail the different hardware components of the system under test which are important to achieve the reported result.

5.1.1 Hardware Vendor

Company which sells the hardware (config.hw.vendor)

5.1.2 Model

The model name identifying the system under test (config.hw.model)

5.1.3 CPU Name

A manufacturer-determined processor formal name. (config.hw.cpu)

5.1.4 CPU Characteristics

Technical characteristics to help identify the processor, such as number of cores, frequency, cache size etc (config.hw.cpu.characteristics).

5.1.5 CPU Frequency (MHz)

The clock frequency of the CPU, expressed in megahertz (config.hw.cpu.mhz).

5.1.6 CPU(s) enabled

The CPUs that were enabled and active during the benchmark run, displayed as the number of cores (config.hw.cpu.cores), the number of chips (config.hw.cpu.chips) and the number of cores per chip (config.hw.cpu.cores_per_chip).

5.1.7 Hardware Threads / Core

The number of hardware threads available per core (config.hw.cpu.threads_per_core).

5.1.8 CPU(s) orderable

The number of CPUs that can be ordered in a system of the type being tested (config.hw.cpu.orderable).

5.1.9 Primary Cache

Description (size and organization) of the CPU's primary cache. This cache is also referred to as "L1 cache" (config.hw.cache.primary).

5.1.10 Secondary Cache

Description (size and organization) of the CPU's secondary cache. This cache is also referred to as "L2 cache" (config.hw.cache.secondary).

5.1.11 Tertiary Cache

Description (size and organization) of the CPU's tertiary, or "L3" cache (config.hw.cache.tertiary).

5.1.12 Other Cache

Description (size and organization) of any other levels of cache memory (config.hw.cache.other).

5.1.13 Memory Amount (GB)

Total size of memory in the SUT in GB (config.hw.memory.gb).

5.1.14 # and size of DIMM(s)

Number and size of memory modules used for testing (config.hw.memory.dimms).

5.1.15 Memory Details

Detailed description of the system main memory technology, such as CAS latencies, frequency, number of ranks, interleaving, etc. (config.hw.memory.description).

5.1.16 Power Supply Quantity and Rating

The number of power supplies that are installed in the tested configuration (config.hw.psu.installed) and the power rating for each power supply (config.hw.psu.rating).

5.1.17 Power Supply Details

The manufacturer of the power supply and the model number to identify it. (config.hw.psu.description).

5.1.18 Disk Drive

A description of the disk drive(s) (size, type, and RAID level if any) used to hold the benchmark software and data during the run (config.hw.disk).

5.1.19 Disk Controller

The manufacturer and model number of the controller used to drive the disk(s) (config.hw.disk.controller).

5.1.20 # and type of Network Interface Cards (NICs) Installed

A description of the network controller(s) (number, manufacturer, type, ports and speed) installed on the SUT (config.hw.network.controller).

5.1.21 NICs Enabled in Firmware / OS / Connected

The number of NICs (ports) enabled in the Firmware, in the OS and actually connected during the test (config.hw.network.controller.enabled).

5.1.22 Network Speed

The network speed actually used on the configured NICs during the test (config.hw.network.speed).

5.1.23 Keyboard

The type of keyboard (USB, PS2, KVM or none) used (config.hw.keyboard).

5.1.24 Mouse

The type of mouse (USB, PS2, KVM or none) used (config.hw.mouse).

5.1.25 Monitor

Specifies if a monitor was used for the test and how it was connected (directly or via KVM) (config.hw.monitor).

5.1.26 Optical Drives

Specifies whether any optical drives were configured in the SUT (config.hw.optical).

5.1.27 Other Hardware

Any additional equipment added to improve performance and required to achieve the reported scores (config.hw.other).

5.2 Software

This section describes in detail the various software components installed on the system under test, which are important to achieve the reported result, and their configuration parameters.

5.2.1 Power Management

This field shows whether power management features of the SUT were enabled or disabled (config.sw.power_management).

5.2.2 Operating System

The operating system name (config.sw.os).

5.2.3 OS Version

The operating system version. If there are patches applied that affect performance, they must be disclosed in the System Under Test Notes (config.sw.os.version).

5.2.4 File System

The type of the filesystem used to contain the run directories (config.sw.filesystem).

5.2.5 JVM Vendor

The company that makes the JVM software. (config.sw.jvm.vendor)

5.2.6 JVM Version

Name and version of the JVM software product. (config.sw.jvm.version)

5.2.7 JVM Options

JVM command-line options used when invoking the benchmark. (config.sw.jvm.options)

5.2.8 JVM Affinity

Commands used to configure affinity for each JVM (config.sw.jvm.affinity)

5.2.9 JVM Instances

The quantitiy of JVm instances running. This number is detected automatically by the benchmark program and reported here.

5.2.10 JVM Initial Heap Memory (MB)

How many megabytes initially used by the JVM heap. "Unlimited" or "dynamic" are allowable values for JVMs that adjust automatically (config.sw.jvm.heap.initial).

5.2.11 JVM Maximum Heap Memory (MB)

How many megabytes can maximally be used by the JVM heap. "Unlimited" or "dynamic" are allowable values for JVMs that adjust automatically (config.sw.jvm.heap.max).

5.2.12 JVM Address Bits

The basic pointer size (32 or 64 bit) used by the installed JVM (config.sw.jvm.bitness).

5.2.13 Benchmark Version

The version of the benchmark kit used to produce this result. This information is provided automatically by the benchmark software.

5.2.14 Director Location

Indentifies the system which hosts the director controlling the different JVM instances (SUT, CCS or other). Locations other than SUT or CCS require additional description under Notes (config.director.location).

5.2.15 Other Software

Any performance-relevant software used and required to reproduce the reported scores, including third-party libraries, accelerators, etc. (config.sw.other)

6. System Under Test Notes

Free text description of what sort of tuning one has to do to either the OS or the JVM to get these results. Also additional hardware information not covered in the other fields above can be given here.
The following list shows examples of information that must be reported in this section:

• System tuning parameters other than default.
• Process tuning parameters other than default.
• Changes to the background load, if any.
• Critical customer-identifiable firmware or option versions such as network and disk controllers.
• Definitions of tuning parameters must be included.
• Part numbers or sufficient information that would allow the end user to order the SUT configuration.
• Identification of any components used that are supported but that are no longer orderable by ordinary customers.

7. Controller System

The next section of the report file describes the hardware and the software of the system running the controller.

7.1 Hardware

This part of the report contains a brief overview of the hardware used to run the SPECpower Control and Collection System (CCS).

7.1.1 Hardware Vendor

Company which sells/manufactures the controller hardware (ccs.config.hw.vendor)

7.1.2 Model

The model name identifying the system running the controller (ccs.config.hw.model)

7.1.3 CPU Description

The name of the processor installed in the controller system (ccs.config.hw.cpu) and some technical characteristics to help identify the processor, such as number of cores, frequency, cache size etc (ccs.config.hw.cpu.characteristics)

7.1.4 Memory amount (GB)

Total size of memory in the controller system in GB (ccs.config.hw.memory.gb)

7.2 Software

Main software components installed on the controller system.

7.2.1 Operating System (OS)

The name and the version of the operating system installed on controller system (ccs.config.sw.os)

7.2.2 JVM Vendor

The company which makes the JVM software (ccs.config.sw.jvm.vendor)

7.2.3 JVM Version

Name and version of the JVM software product. (ccs.config.sw.jvm.version)

7.2.4 CCS Version

The version of the controller program used to produce this result. This information is provided automatically by the benchmark software.

8. Measurement Devices

This section of the report shows the details of the different measurement devices used for this benchmark run.

8.1 Power Analyzer

The following table includes information about the power analyzer used to measure the electrical data.

8.1.1 Hardware Vendor

Company which manufactures and/or sales the power analyzer (ptd.pwrN.config.analyzer.vendor)

8.1.2 Model

The model name of the power analyzer type used for this benchmark run (ptd.pwrN.config.analyzer.model)

8.1.3 Serial Number

The serial number uniquely identifying the power analyzer used for this benchmark run (ptd.pwrN.config.analyzer.serial)

8.1.4 Connectivity

Which interface was used to connect the power analyzer to the PTD host system and to read the power data, e.g. RS-232 (serial port), USB, GPIB etc. (ptd.pwrN.config.analyzer.connectivity)

8.1.5 Current Range

Value of current range setting to which power analyzer has been configured, or "Auto" if none (ptd.pwrN.config.analyzer.current_range).

8.1.6 Voltage Range

Value of voltage range setting to which power analyzer has been configured, or "Auto" if none (ptd.pwrN.config.analyzer.voltage_range).

8.1.7 Input Connection

Input connection used to connect the load, if several options are available, or "Default" if not (ptd.pwrN.config.analyzer.input_connection).

8.1.8 Calibration Institute

Name of the national metrology institute which specifies the calibration standards for power analyzers (ptd.pwrN.config.calibration.institute)

8.1.9 Accredited by

Name of the organization that performed the power analyzer calibration according to the standards defined by the national metrology institute. Could be the analyzer manufacturer, a third party company, or an organization within your own company (ptd.pwrN.config.calibration.accredited_by).

8.1.10 Calibration Label

A number which uniquely identifies this meter calibration event. May appear on the calibration certificate or on a sticker applied to the power analyzer. The format of this number is specified by the calibration institute (ptd.pwrN.config.calibration.label).

8.1.11 Date of Calibration

The date the calibration certificate was issued, from the calibration label or the calibration certificate (ptd.pwrN.config.calibration.date).

8.1.12 Power Daemon Host System

The manufacturer and model number of the system connected to power analyzer and running the power daemon (ptd.pwrN.config.ptd.system).

8.1.13 Power Daemon Host OS

The name and the version of the operating system installed on the power daemon host system (ptd.pwrN.config.ptd.os)

8.1.14 Power Daemon Version

The version of the power daemon program reading the analyzer data, including CRC information to verify that the released version was running unchanged. This information is provided automatically by the benchmark software.

8.2 Temperature Sensor

The following table includes information about the temperature sensor used to measure the ambient temperature of the test environment.

8.2.1 Hardware Vendor

Company which manufactures and/or sales the temperature sensor (ptd.tempN.config.sensor.vendor)

8.2.2 Model

The manufacturer and model name of the temperature sensor used for this benchmark run (ptd.tempN.config.sensor.model)

8.2.3 Driver Version

The version number of the operating system driver used to control and read the temperature sensor (ptd.tempN.config.sensor.driver)

8.2.4 Connectivity

Which interface was used to read the temperature data from the sensor, e.g. RS-232 (serial port), USB etc. (ptd.tempN.config.sensor.connectivity)

8.2.5 Power Daemon Host System

The manufacturer and model number of the system connected to temperature sensor and running the temperature daemon (ptd.tempN.config.ptd.system)

8.2.6 Power Daemon Host OS

The name and the version of the operating system installed on the temperature daemon host system (ptd.tempN.config.ptd.os)

9. Notes

Additional important information required to reproduce the results from other reporting sections, i.e. not related to the SUT, that require a larger text area.
Any power and/or voltage range selections that have been set manually on the power analyzer must be reported here (config.notes).

10. Electrical and Environmental Data

The following section displays more details of the electrical and environmental data collected during the different target loads, including data not used to calculate the benchmark result. For further explanation of the measured values look in the "SPECpower Methodology" document.

10.1 Target Load

Load levels as described in paragraph Target Load

10.2 Electrical Data

Additional power related data measured by the power analyzer. All values are measured in one second intervals, aggregated by the power daemon and reported to the collection system at the end of each target load level.

10.2.1 Average Voltage (V)

Average voltage for each of the target load levels measured in Volt (V).

10.2.2 Average Current (A)

Average current for each of the target load levels measured in Ampere (A).

10.2.3 Average Power Factor

Average power factor for each of the target load levels (PF).

10.2.4 Average Power (W)

Average power for each target load level as described in paragraph Average Power (W)

10.2.5 Line Standard

Description of the line standards for the main AC power as provided by the local utility company and used to power the SUT. The standard voltage and frequency are printed in this field followed by the number of phases and wires used to connect the SUT to the AC power line.

10.2.6 Average Power Factor

Power factor average over all target load levels.

10.3 Environmental Data

Environmental data describing the conditions present during the time of the measurement.

10.3.1 Minimum Ambient Temperature (°C)

The ambient temperature for each of the target load levels measured by the temperature sensor. All values are measured in ten second intervals, evaluated by the temperature daemon and reported to the collection system at the end of each target load level.

10.3.2 Minimum Temperature (°C)

Minimum temperature which was measured by the temperature sensor during all taget load levels.

10.3.3 Elevation (m)

Elevation of the location where the test was run. This inforamtion is provided by the tester (config.test.elevation)

11. Aggregate Performance Data

This section describes the aggregated throughput for all JVM instances measured during all test phases including the calibration intervals in a table and as a graph.

11.0.1 Target Load

Load levels as described in paragraph Target Load plus the calibration phases at the beginning. The number of calibration phases can be configured by the tester (config.input.calibration.interval_count), minimum = 3, maximum = 10.

11.0.2 Actual Load

This column shows the actual target loads as described in paragraph Actual Load.

11.1 ssj_ops

The throughput scores both, target and actual values, for all test phases are printed in two columns.

11.1.1 Target

The target throughput for the measurement phases calculated from the calibrated maximum throughput ssj_ops@calibrated=.

11.1.2 Actual

The actual throughput measured during all test phases including calibration as described in paragraph ssj_ops.

11.1.3 ssj_ops@calibrated=

The calibrated throughput is calculated from the average throughput of the last two calibration phases. It is required to run at least three calibration phases and at most ten (config.input.calibration.interval_count).

11.2 ssj_ops Chart

The result chart graphically displays the throughput results reported in the aggregate performance data table in one diagram. The blue line with the square data points represents the target values and the red line with the rotund data points represents the actually measured throughput values for the different test phases as indicated on the x-axis. The throughput values are shown on the y-axis, higher values are better. The thin horizontal line at the top shows the maximal throughput calculated from the calibration runs.

12. Aggregate Performance Report

This is the second part of the SPECpower_ssj2008 full disclosure report revising the configuration information and aggregate performance numbers from the first part plus adding more detailed performance information if more than one JVM instance was started.
This report is not created for benchmark runs using only one JVM instance. In this case only the VM Instance Performance Report is generated.

12.1 Top bar

This section shows the measured SPECpower_ssj2008 result and gives some general information regarding this test run. For more details see section Top bar.

12.2 Benchmark Results Summary

This section describes the aggregated throughput for all JVM instances measured during all test phases including the calibration intervals in a table and as a graph. For more details see section Aggregate Performance Data.

12.3 System Under Test

This section of the report file describes the hardware and the software of the system under test (SUT) used to run the reported SPECpower benchmark with the level of detail required to reproduce this result. For more details see section System Under Test.

12.4 System Under Test Notes

Free text description of any tunings required to achieve the reported result. For more details see section System Under Test Notes.

12.5 Notes

A description of all configuration settings that have been changed from the default values. For more details see section Notes.

13. JVM Instance Summary

This section shows the overall throughput result and the individual result for each JVM instance in a table and as a chart.

13.0.1 JVM Instance

This column of the table names the different JVM instances, the aggregated throughput at 100% target load and the average throughput per JVM instance at 100% target load.

13.0.2 ssj_ops@100%

The aggregated throughput for all JVM instances at the 100% target load lavel.

13.0.3 ssj_ops@100% per JVM

The calculated throughput for one JVM at the 100% target load level. This value is the average of the individual scores for each JVM instance at 100% target load as displayed above.

13.0.4 Aggr. JVM ssj_ops Chart

Result chart graphically displaying the throughput achieved by the different JVM instances. For more details see section ssj_ops Chart.

14. JVM Instance Scores

For each of the JVM instances there is a section describing the throughput measured during all test phases in a table and as a chart. For more details see section Aggregate Performance Data.

14.0.1 Target Load

For description see Target Load.

14.0.2 Actual Load

For description see Actual Load.

14.1 ssj ops

For description see ssj_ops.

14.1.1 Target

For description see Target.

14.1.2 Actual

For description see Actual.

14.1.3 ssj_ops@calibrated=

For description see ssj_ops@calibrated=.

14.2 ssj_ops Chart

For description see ssj_ops Chart.

15. JVM Instance Performance Report

This is the third part of the SPECpower_ssj2008 full disclosure report revising the configuration information and performance numbers from the second part plus adding more detailed throughput information for different transaction types. There may exist several of these reports, one for each JVM instance.

15.1 Top bar

This section shows the measured SPECpower_ssj2008 result and gives some general information regarding this test run. For more details see section Top bar.

15.2 Benchmark Results Summary

This section describes the aggregated throughput for this specific JVM instance measured during all test phases including the calibration intervals in a table and as a graph. For more details see section Aggregate Performance Data.

15.3 System Under Test

This section of the report file describes the hardware and the software of the system under test (SUT) used to run the reported SPECpower benchmark with the level of detail required to reproduce this result. For more details see section System Under Test.

15.4 System Under Test Notes

Free text description of any tunings required to achieve the reported result. For more details see section System Under Test Notes.

15.5 Notes

A description of all configuration settings that have been changed from the default values. For more details see section Notes.

16. Performance Details

This table gives more details about the transactions executed during the different test phases by this JVM instance.

16.0.1 Target Load

For description see Target Load.

16.0.2 Actual Load

For description see Actual Load.

16.0.3 Transaction Type

This column of the table names the different transaction types which are executed by the workload.

16.0.4 Count

This column of the table displays the count of successfully finished transactions during the different test phases separately for each type.

16.0.5 Total Heap (MB)

The total amount of heap memory used by this JVM instance during the different test phases.

Copyright © 2007 Standard Performance Evaluation Corporation
All Rights Reserved