Hewlett-Packard Company

Transcription

1 Hewlett-Packard Company TPC Benchmark H Full Disclosure Report for HP ProLiant DL785 G6 using Microsoft SQL Server 2008 Enterprise Edition SP1 for x64 and Windows Server 2008 R2 Enterprise Edition for x64 Second Edition February 2010 i

2 Hewlett-Packard Company (HP), the Sponsor of this benchmark test, believes that the information in this document is accurate as of the publication date. The information in this document is subject to change without notice. The Sponsor assumes no responsibility for any errors that may appear in this document. The pricing information in this document is believed to accurately reflect the current prices as of the publication date. However, the Sponsor provides no warranty of the pricing information in this document. Benchmark results are highly dependent upon workload, specific application requirements, and system design and implementation. Relative system performance will vary as a result of these and other factors. Therefore, the TPC Benchmark H should not be used as a substitute for a specific customer application benchmark when critical capacity planning and/or product evaluation decisions are contemplated. All performance data contained in this report was obtained in a rigorously controlled environment. Results obtained in other operating environments may vary significantly. No warranty of system performance or price/performance is expressed or implied in this report. Copyright 2010 Hewlett-Packard Company. All rights reserved. Permission is hereby granted to reproduce this document in whole or in part provided the copyright notice printed above is set forth in full text or on the title page of each item reproduced. Printed in the United States, February, 2010 HP and HP StorageWorks are registered trademarks of Hewlett-Packard Company. Microsoft, Windows 2008 and SQL Server 2008 are registered trademarks of. TPC Benchmark, TPC-H, QppH, QthH and QphH are registered certification marks of the Transaction Processing Performance Council. All other brand or product names mentioned herein must be considered trademarks or registered trademarks of their respective owners. ii

3 Abstract Overview This report documents the methodology and results of the TPC Benchmark H test conducted on the HP ProLiant DL785 G6 using Microsoft SQL Server 2008 Enterprise Edition SP1 for x64 in conformance with the requirements of the TPC Benchmark H Standard Specification, Revision The operating system used for the benchmark was Microsoft Windows Server 2008 R2 Enterprise Edition for x64. The TPC Benchmark H was developed by the Transaction Processing Performance Council (TPC). The TPC was founded to define transaction processing benchmarks and to disseminate objective, verifiable performance data to the industry. TPC Benchmark H Full Disclosure Report and other information can be downloaded from the Transaction Processing Performance Council web site at Standard and Executive Summary Statements Pages iv - vii contain the Executive Summary and Numerical Quantities Summary of the benchmark results for the HP ProLiant DL785 G6. Auditor The benchmark configuration, environment and methodology used to produce and validate the test results, and the pricing model used to calculate the cost per QppH and QthH were audited by Lorna Livingtree of Performance Metrics, Inc. to verify compliance with the relevant TPC specifications. The auditor s letter of attestation is attached in Section 9.1 Auditors Report. iii

4 HP ProLiant DL785 G6 TPC-H Rev Report Date: November 9, 2009 Revision Date: February 5, 2010 Total System Cost Composite Query per Hour Rating Price Performance $236,233 USD 81,514.8 QphH $2.90 USD $ 1000G Database size Database Manager Operating System Other Software Availability Date 1000GB SQL Server 2008 Enterprise Edition Windows Server 2008 R2 Enterprise Edition None November 9, 2009 RF2 RF1 Q22 Q21 Q20 Q19 Q18 Q17 Q16 Q15 Q14 Q13 Q12 Q11 Q10 Q9 Q8 Q7 Q6 Q5 Q4 Q3 Q2 Q Query Times in seconds Geometric Mean of Power Test Arithmetic Mean of Throughput Test Power Run Throughput Run Database Load Time = 4h34m30s Load included backup: Y Total Data Storage / Database Size = RAID(Base Tables): n.a. RAID (Base Tables and Auxiliary Data Structure): n.a. RAID(All)= Y System Components System Total Per Node Nodes: 1 n.a. AMD Opteron 8439 Six-Core 2.8GHz: 8 8 Cores: Threads: Memory: 512GB 512GB OS Disk Drives(internal): 6 6 Network Interfaces (on-board GigE): 2 2 Storage Controllers P800: 6 6 Storage Shelves MSA70: 12 n.a. Storage Subsystem Disk Drives: 240 n.a. Total Storage: 16, GB n.a. iv

5 Server Hardware Description HP ProLiant DL785 G6 Price Key Part Number TPC-H Rev Report Date: November 9, 2009 Revision Date: February 5, 2010 Unit Price Qty. Extended Price HP DL785 CTO Chassis 1 AH233A $9,999 1 $9,999 HP O8439SE 2.8GHz DL785 4p FIO Kit L21 $19,499 1 $19,499 HP O8439SE 2.8GHz DL785 4p Kit B21 $19,499 1 $19,499 HP 64GB Reg PC x8GB B21 $7,199 8 $57,592 HP 36GB 15k 2.5 Single Port HP SAS Drive B21 $349 2 $698 3 Yr Maint Price HP 72GB 15k 2.5 Single Port HP SAS Drive B21 $359 4 $1,436 HP 3year 4h 24x7 Proliant DL785 HW Support 1 HA104A3 Opt.6XP $3,208 1 $3,208 HP 17" FlatPanel Monitor 1 GV537A8 $130 1 $130 HP USB Keyboard 1 GM321AA#ABA $14 1 $14 HP Optical 4 Button USB Mouse 1 EW208AA#ABA $7 1 $7 Storage Subtotal $108,874 $3,208 HP 5642 Unassembled Rack B21 $865 1 $865 HP Smart Array Controller P B21 $949 6 $5,694 Storage MSA B21 $3, $38,388 Storage MSA70 10% Spares B21 $3,199 2 $6,398 HP ext Mini SAS 4m Cable B21 $ $1,704 HP 72GB 15k 2.5 Single Port HP SAS Drive B21 $ $86,160 HP 72GB 15k 2.5 Single Port HP SAS Drive 10% spares B21 $ $8,616 Server Software Subtotal $147,825 $0 Microsoft Windows Server 2008 R2 Enterprise Edition 2 LSA $2,328 1 $2,328 Microsoft SQL Server 2008 Enterprise x64 Edition with 25 CALs $8,318 1 $8,318 $245 Microsoft SQL Server 2008 Client License $ $7,020 Price Key: 1 - HP, 2 - Microsoft, Audited by Lorna Livingtree of Performance Metrics, Inc Subtotal $17,666 $245 Total Extended Price $274,365 $3,453 Total Discounts $41,072 $513 Grand Total $233,293 $2,940 All discounts are based on US list prices and for similar quantities and configurations. A 16% discount was based on the overall specific components pricing from vendor 1 in this single quotation. Discounts for similarly sized configurations will be similar to those quoted here, but may vary based on the components in the configuration. 3 year cost of ownership USD: $236, GB: 81,514.8 $ 1000GB $2.90 Sales contact: HP Sales Development, Pruneridge Ave., Cupertino, CA (408) or H-P direct: Prices used in TPC benchmarks reflect the actual prices a customer would pay for a one-time purchase of the stated components. Individually negotiated discounts are not permitted. Special prices based on assumptions about past or future purchases are not permitted. All discounts reflect standard pricing policies for the listed components. For complete details, see the pricing sections of the TPC benchmark specifications. If you find that the stated prices are not available according to these terms, please inform at pricing@tpc.org. Thank you. v

6 HP ProLiant DL785 G6 TPC-H Rev Report Date: November 9, 2009 Revision Date: February 5, 2010 Numerical Quantities Measurement Results Database Scale Factor 1000GB Total Data Storage / Database Size Start of Database Load 10/27/09 9:46:24 End of Database Load 10/27/09 14:20:54 Database Load Time 4h 34m 30s Query Streams for Throughput Test 7 TPC-H Power 95,789.1 TPC-H Throughput 69,367.6 TPC-H Composite Query-per-Hour (QphH@1000GB) 81,514.8 Total System Price over 3 Years $236,233 TPC-H Price/Performance Metric (USD / QphH@1000GB) $2.90 / QphH@1000GB Measurement Interval Measurement Interval in Throughput Test (Ts) = seconds 7992 seconds Duration of Stream Execution Power Stream Seed RF1 Start Time Query Start Time RF2 Start Time RF1 End Time Query End Time RF2 End Time 10/27/09 18:46:12 10/27/09 18:50:52 10/27/09 19:16:11 10/27/09 18:47:41 10/27/09 19:16:11 10/27/09 19:17:10 Duration 0:30:58 Throughput Stream Seed Query Start Time RF1 Start Time RF2 Start Time Duration Query End Time RF1 End Time RF2 End Time 10/27/09 19:20:12 10/27/09 21:17:56 10/27/09 21:19:41 2:00:35 10/27/09 21:12:30 10/27/09 21:19:41 10/27/09 21:20:47 10/27/09 19:20:12 10/27/09 21:20:48 10/27/09 21:22:04 2:02:55 10/27/09 21:17:55 10/27/09 21:22:03 10/27/09 21:23:08 10/27/09 19:20:13 10/27/09 21:23:09 10/27/09 21:24:17 2:05:03 10/27/09 21:10:54 10/27/09 21:24:16 10/27/09 21:25:15 10/27/09 19:20:13 10/27/09 21:25:16 10/27/09 21:26:19 2:07:03 10/27/09 21:13:38 10/27/09 21:26:19 10/27/09 21:27:16 10/27/09 19:20:14 10/27/09 21:27:17 10/27/09 21:28:18 2:09:04 10/27/09 21:16:27 10/27/09 21:28:17 10/27/09 21:29:17 10/27/09 19:20:14 10/27/09 21:29:18 10/27/09 21:30:23 2:11:08 10/27/09 21:16:40 10/27/09 21:30:22 10/27/09 21:31:22 10/27/09 19:20:14 10/27/09 21:31:23 10/27/09 21:32:24 2:13:10 10/27/09 21:14:28 10/27/09 21:32:23 10/27/09 21:33:24 vi

7 HP ProLiant DL785 G6 TPC-H Rev Report Date: November 9, 2009 Revision Date: February 5, 2010 TPC-H Timing Intervals (in seconds): Stream Stream Stream Stream Stream Stream Stream Stream Min Max Avg Qi Qi Qi Q , , , , , , , , , ,078.8 Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q , , , , , ,090.7 Q Q Q , , , , , , , ,055.9 Q UF UF vii

8 Abstract...iii Overview...iii Standard and Executive Summary Statements...iii Auditor...iii 1.0 General Items Test Sponsor Parameter Settings Configuration Items Clause 1: Logical Database Design Table Definitions Physical Organization of Database Horizontal Partitioning Replication Clause 2: Queries and Refresh Functions - Related Items Query Language Random Number Generation Substitution Parameters Generation Query Text and Output Data from Database Query Substitution Parameters and Seeds Used Isolation Level Refresh Functions Clause 3: Database System Properties Atomicity Requirements Atomicity of the Completed Transactions Atomicity of Aborted Transactions Consistency Requirements Isolation Requirements Durability Requirements Clause 4: Scaling and Database Population Initial Cardinality of Tables Distribution of Tables and Logs Across Media Mapping of Database Partitions/Replications Implementation of RAID DBGEN Modifications Database Load time Data Storage Ratio Database Load Mechanism Details and Illustration Qualification Database Configuration Dataset Verification Clause 5: Performance Metrics and Execution Rules Related Items Steps after the Load Test Steps in the Power Test Timing Intervals for Each Query and Refresh Function Number of Streams for The Throughput Test Start and End Date/Times for Each Query Stream Total Elapsed Time for the Measurement Interval Refresh Function Start Date/Time and Finish Date/Time Timing Intervals for Each Query and Each Refresh Function for Each Stream Performance Metrics viii

9 6.10 The Performance Metric and Numerical Quantities from Both Runs System Activity Between Tests Clause 6: SUT and Driver Implementation Related Items Driver Implementation Specific Layer (ISL) Profile-Directed Optimization Clause 7: Pricing Related Items Hardware and Software Used Three-Year Cost of System Configuration Availability Dates Clause 8: Audit Related Items Auditors Report Appendix A: Tunable Parameters Appendix B: Database Build Scripts Appendix C: Query Text and Output Appendix D: Seeds and Query Substitution Parameters Appendix E: Refresh Function Source Code Appendix F: Implementation Specific Layer and Source Code Appendix G: Price Quotations

10 1.0 General Items 1.1 Test Sponsor A statement identifying the benchmark sponsor(s) and other participating companies must be provided. This benchmark was sponsored by Hewlett-Packard Company. The benchmark was developed and engineered by Hewlett-Packard Company. Testing took place at Microsoft facilities in Redmond, Washington. 1.2 Parameter Settings Settings must be provided for all customer-tunable parameters and options which have been changed from the defaults found in actual products, including by not limited to: Database Tuning Options Optimizer/Query execution options Query processing tool/language configuration parameters Recovery/commit options Consistency/locking options Operating system and configuration parameters Configuration parameters and options for any other software component incorporated into the pricing structure Compiler optimization options This requirement can be satisfied by providing a full list of all parameters and options, as long as all those which have been modified from their default values have been clearly identified and these parameters and options are only set once. Appendix A, Tunable Parameters, contains a list of all database parameters and operating system parameters. 1.3 Configuration Items Diagrams of both measured and priced configurations must be provided, accompanied by a description of the differences. This includes, but is not limited to: Number and type of processors Size of allocated memory, and any specific mapping/partitioning of memory unique to the test. Number and type of disk units (and controllers, if applicable). Number of channels or bus connections to disk units, including their protocol type. Number of LAN (e.g. Ethernet) Connections, including routers, workstations, terminals, etc., that were physically used in the test or are incorporated into the pricing structure. Type and the run-time execution location of software components (e.g., DBMS, query processing tools /languages, middle-ware components, software drivers, etc.). 10

11 The System Under Test (SUT), an HP ProLiant DL785 G6, depicted in Figure 1.1, consisted of : 8 AMD Opteron 8439 Hex-Core 2.8GHz 512 GB RAM 6 P800 Smart Array Controllers 12 HP StorageWorks MSA 70 Enclosures GB Pluggable SAS Disks 2 36GB Pluggable SAS Disks 6 x P x MSA x 72GB SAS Disks HP ProLiant DL785 G6 Figure 1.1 Benchmark and priced configuration for HP ProLiant DL785 G6 11

12 2.0 Clause 1: Logical Database Design 2.1 Table Definitions Listings must be provided for all table definition statements and all other statements used to set up the test and qualification databases. ( ) Appendix B, Database Build Scripts, contains the table definitions and the program used to load the database. 2.2 Physical Organization of Database The physical organization of tables and indices, within the test and qualification databases, must be disclosed. If the column ordering of any table is different from that specified in Clause 1.4, it must be noted. Appendix B, Database Build Scripts, contains the DDL for the index definitions. 2.3 Horizontal Partitioning Horizontal partitioning of tables and rows in the test and qualification databases (see Clause 1.5.4) must be disclosed. Horizontal partitioning was not used 2.4 Replication Any replication of physical objects must be disclosed and must conform to the requirements of Clause No replication was used. 12

13 3.0 Clause 2: Queries and Refresh Functions - Related Items 3.1 Query Language The query language used to implement the queries must be identified. T-SQL was the query language used. 3.2 Random Number Generation The method of verification for the random number generation must be described unless the supplied DBGEN and QGEN were used. DBGEN version and QGEN version were used to generate all database populations. 3.3 Substitution Parameters Generation The method used to generate values for substitution parameters must be disclosed. If QGEN is not used for this purpose, then the source code of any non-commercial tool used must be disclosed. If QGEN is used, the version number, release number, modification number and patch level of QGEN must be disclosed. The TPC source based QGEN version was used to generate the substitution parameters 3.4 Query Text and Output Data from Database The executable query text used for query validation must be disclosed along with the corresponding output data generated during the execution of the query text against the qualification database. If minor modifications (see Clause 2.2.3) have been applied to any functional query definitions or approved variants in order to obtain executable query text, these modifications must be disclosed and justified. The justification for a particular minor query modification can apply collectively to all queries for which it has been used. The output data for the power and throughput tests must be made available electronically upon request.. Appendix C contains the query text and query output. The following modifications were used: o The dateadd function is used to perform date arithmetic in Q1, Q4, Q5, Q6, Q10, Q12, Q14, Q15 and Q20. o The datepart function is used to extract part of a date ( YY ) in Q7, Q8 and Q9. o The top function is used to restrict the number of output rows in Q2, Q3, Q10, Q18 and Q21 o The countbig function is used in place of count in Q1 3.5 Query Substitution Parameters and Seeds Used All the query substitution parameters used during the performance test must be disclosed in tabular format, along with the seeds used to generate these parameters. Appendix D contains the seed and query substitution parameters used. 3.6 Isolation Level The isolation level used to run the queries must be disclosed. If the isolation level does not map closely to one of the isolation levels defined in Clause 3.4, additional descriptive detail must be provided. The queries and transactions were run with isolation level Read Committed. 3.7 Refresh Functions The details of how the refresh functions were implemented must be disclosed Appendix E contains the source code for the refresh functions. 13

14 4.0 Clause 3: Database System Properties 4.1 Atomicity Requirements The results of the ACID tests must be disclosed along with a description of how the ACID requirements were met. This includes disclosing the code written to implement the ACID Transaction and Query. All ACID tests were conducted according to specification. The steps performed are outlined below Atomicity of the Completed Transactions Perform the ACID Transaction for a randomly selected set of input data and verify that the appropriate rows have been changed in the ORDER, LINEITEM, and HISTORY tables. The following steps were performed to verify the Atomicity of completed transactions: 1. The total price from the ORDER table and the extended price from the LINEITEM table were retrieved for a randomly selected order key. 2. The ACID Transaction was performed using the order key from step The ACID Transaction committed. 4. The total price from the ORDER table and the extended price from the LINEITEM table were retrieved for the same order key. It was verified that the appropriate rows had been changed Atomicity of Aborted Transactions Perform the ACID transaction for a randomly selected set of input data, submitting a ROLLBACK of the transaction for the COMMIT of the transaction. Verify that the appropriate rows have not been changed in the ORDER, LINEITEM, and HISTORY tables. The following steps were performed to verify the Atomicity of the aborted ACID transaction: 1. The total price from the ORDER table and the extended price from the LINEITEM table were retrieved for a randomly selected order key. 2. The ACID Transaction was performed using the order key from step 1. The transaction was stopped prior to the commit. 3. The ACID Transaction was ROLLED BACK.. 4. The total price from the ORDER table and the extended price from the LINEITEM table were retrieved for the same order key used in steps 1 and 2. It was verified that the appropriate rows had not been changed. 4.2 Consistency Requirements Consistency is the property of the application that requires any execution of transactions to take the database from one consistent state to another. A consistent state for the TPC-H database is defined to exist when: OTOTALPRICE = SUM(trunc(trunc((LEXTENDEDPRICE LDISCOUNT) * (1 + LTAX))) for each ORDER and LINEITEM defined by (OORDERKEY = LORDERKEY) Consistency Tests Verify that ORDER and LINEITEM tables are initially consistent as defined in Clause , based upon a random sample of at least 10 distinct values of OORDERKEY. The following steps were performed to verify consistency: 1. The consistency of the ORDER and LINEITEM tables was verified based on a sample of OORDERKEYs. 2. One hundred ACID Transactions were submitted from each of six execution streams. 3. The consistency of the ORDER and LINEITEM tables was re-verified. 14

15 4.3 Isolation Requirements Operations of concurrent transactions must yield results which are indistinguishable from the results which would be obtained by forcing each transaction to be serially executed to completion in some order Isolation Test 1 - Read-Write Conflict with Commit Demonstrate isolation for the read-write conflict of a read-write transaction and a read-only transaction when the read-write transaction is committed) The following steps were performed to satisfy the test of isolation for a read-only and a read-write committed transaction: 1. An ACID Transaction was started for a randomly selected OKEY, LKEY and DELTA. The ACID Transaction was suspended prior to Commit. 2. An ACID query was started for the same OKEY used in step 1. The ACID query blocked and did not see any uncommitted changes made by the ACID Transaction. 3. The ACID Transaction was resumed and committed. The ACID query completed. It returned the data as committed by the ACID Transaction Isolation Test 2 - Read-Write Conflict with Rollback Demonstrate isolation for the read-write conflict of a read-write transaction and a read-only transaction when the read-write transaction is rolled back. The following steps were performed to satisfy the test of isolation for read-only and a rolled back read-write transaction: 1. An ACID transaction was started for a randomly selected OKEY, LKEY and DELTA. The ACID Transaction was suspended prior to Rollback. 2. An ACID query was started for the same OKEY used in step 1. The ACID query did not see any uncommitted changes made by the ACID Transaction. 3. The ACID Transaction was ROLLED BACK. 4. The ACID query completed Isolation Test 3 - Write-Write Conflict with Commit Demonstrate isolation for the write-write conflict of two update transactions when the first transaction is committed. The following steps were performed to verify isolation of two update transactions: 1. An ACID Transaction T1 was started for a randomly selected OKEY, LKEY and DELTA. The ACID transaction T1 was suspended prior to Commit. 2. Another ACID Transaction T2 was started using the same OKEY and LKEY and a randomly selected DELTA. 3. T2 waited. 4. The ACID transaction T1 was allowed to Commit and T2 completed. 5. It was verified that: T2.LEXTENDEDPRICE = T1.LEXTENDEDPRICE +(DELTA1*(T1.LEXTENDEDPRICE/T1.LQUANTITY)) Isolation Test 4 - Write-Write Conflict with Rollback Demonstrate isolation for the write-write conflict of two update transactions when the first transaction is rolled back. The following steps were performed to verify the isolation of two update transactions after the first one is rolled back: 1. An ACID Transaction T1 was started for a randomly selected OKEY, LKEY and DELTA. The ACID Transaction T1 was suspended prior to Rollback. 2. Another ACID Transaction T2 was started using the same OKEY and LKEY used in step 1 and a randomly selected DELTA. 3. T2 waited. 4. T1 was allowed to ROLLBACK and T2 completed. 15

16 5. It was verified that T2.LEXTENDEDPRICE = T1.LEXTENDEDPRICE Isolation Test 5 Concurrent Read and Write Transactions on Different Tables Demonstrate the ability of read and write transactions affecting different database tables to make progress concurrently. The following steps were performed: 1. An ACID Transaction T1 for a randomly selected OKEY, LKEY and DELTA. The ACID Transaction T1 was suspended prior to Commit. 2. Another ACID Transaction T2 was started using random values for PSPARTKEY and PSSUPPKEY. 3. T2 completed. 4. T1 completed and the appropriate rows in the ORDER, LINEITEM and HISTORY tables were changed Isolation Test 6 Update Transactions During Continuous Read-Only Query Stream Demonstrate the continuous submission of arbitrary (read-only) queries against one or more tables of the database does not indefinitely delay update transactions affecting those tables from making progress. The following steps were performed: 1. An ACID Transaction T1 was started, executing Q1 against the qualification database. The substitution parameter was chosen from the interval [ ] so that the query ran for a sufficient amount of time. 2. Before T1 completed, an ACID Transaction T2 was started using randomly selected values of OKEY, LKEY and DELTA. 3. T2 completed before T1 completed. 4. It was verified that the appropriate rows in the ORDER, LINEITEM and HISTORY tables were changed. 16

17 4.4 Durability Requirements The tested system must guarantee durability: the ability to preserve the effects of committed transactions and insure database consistency after recovery from any one of the failures listed in Clause Permanent Unrecoverable Failure of Any Durable Medium and Loss of System Power Guarantee the database and committed updates are preserved across a permanent irrecoverable failure of any single durable medium containing TPC-H database tables or recovery log tables The test database log was stored on 48 logical volumes on RAID-5 array of 5 physical disks. The tables for the test database were stored on 48 logical volumes on RAID-5 arrays. A backup of the test database was taken. The backup was spread across 48 logical volumes on RAID-5 arrays. The tests were conducted on the qualification database. The qualification database was loaded in the same fashion as the test database but used fewer disks. The steps performed are shown below: 1. The complete database was backed up. 2. Eight streams of ACID transactions were started. Each stream executed a minimum of 100 transactions. 3. While the test was running, one of the disks from the database/log array was removed. 4. It was determined that the test kept on running. 5. The eight streams of ACID transactions finished successfully, i.e. the durability requirement of preservation of the database after loss of a single durable medium was fulfilled System Crash Guarantee the database and committed updates are preserved across an instantaneous interruption (system crash/system hang) in processing which requires the system to reboot to recover. 1. Eight streams of ACID transactions were started. Each stream executed a minimum of 100 transactions. 2. While the streams of ACID transactions were running a system hardware reset was issued. 3. The system rebooted and the database was restarted. 4. The database went through a recovery period. 5. The success file and the HISTORY table counts were compared and were found to match. In addition to the hardware reset a Power Failure was also simulated 6. Eight streams of ACID transactions were started. Each stream executed a minimum of 100 transactions. 7. While the streams of ACID transactions were running AC power to the system was removed. 8. When Power was restored the system rebooted and the database was restarted. 9. The database went through a recovery period. 10. The success file and the HISTORY table counts were compared and were found to match Memory Failure Guarantee the database and committed updates are preserved across failure of all or part of memory (loss of contents). See section

18 5.0 Clause 4: Scaling and Database Population 5.1 Initial Cardinality of Tables The cardinality (i.e., the number of rows) of each table of the test database, as it existed at the completion of the database load (see clause 4.2.5) must be disclosed. Table 5.1 lists the TPC-H Benchmark defined tables and the row count for each table as they existed upon completion of the build. TABLE # of Rows Lineitem 5,999,989,709 Orders 1,500,000,000 Partsupp 800,000,000 Part 200,000,000 Customer 150,000,000 Supplier 10,000,000 Nation 25 Region 5 Table 5.1 Initial Number of Rows 5.2 Distribution of Tables and Logs Across Media The distribution of tables and logs across all media must be explicitly described for the tested and priced systems. Microsoft SQL Server was configured on an HP ProLiant DL785 G6 with the following configuration: 6 P800 Smart Array Controllers 12 HP StorageWorks MSA 70 Enclosures GB SAS Disks 2 36GB SAS Disks 240 disks were used to hold table data, indexes, database log and the temporary database (TempDB). The raw partitions for the database and the NTFS partition for the backup and flat files were mounted to a folder on the G: drive G:\mnt\li G:\mnt\gen G:\mnt\temp G:\mnt\ntfs A description of distribution of database filegroups and log can be found in the Table below. 18

19 Slot # of Array Fault Size in Partition Controller/Channel Disks Tolerance GB Format Content Slot 0 2 RAID 1 36 NTFS OS, SQL P400 (onboard) 2 RAID 1 72 NTFS Tools, Mount Points 2 RAID1 72 NTFS TempDB Log Slot 1 A/B 50 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log Slot 5 A/B 50 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log Slot 8 A/B 50 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log Slot 9 A/B 25 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log Slot 10 A/B 30 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log Slot 11 A/B 35 RAID 5 RAW TPCH1000G LI P800 RAW TPCH1000G GEN RAW TPCH1000G TempDB RAID 5 NTFS Backup, Log 19

20 5.3 Mapping of Database Partitions/Replications The mapping of database partitions/replications must be explicitly described. Database partitioning/replication was not used. 5.4 Implementation of RAID Implementations may use some form of RAID to ensure high availability. If used for data, auxiliary storage (e.g. indexes) or temporary space, the level of RAID used must be disclosed for each device. RAID 5 was used for database filegroups, TempDB, for the database recovery logs and for the Backup drives. 5.5 DBGEN Modifications The version number, release number, modification number, and patch level of DBGEN must be disclosed. Any modifications to the DBGEN (see Clause 4.2.1) source code must be disclosed. In the event that a program other than DBGEN was used to populate the database, it must be disclosed in its entirety. DBGEN version was used, no modifications were made. 5.6 Database Load time The database load time for the test database (see clause 4.3) must be disclosed. The database load time was 4h34m30s 5.7 Data Storage Ratio The data storage ratio must be disclosed. It is computed by dividing the total data storage of the priced configuration (expressed in GB) by the size chosen for the test database as defined in The ratio must be reported to the nearest 1/100th, rounded up. Disk Type # of Disks Total (GB) 36 GB 15K rpm SAS GB 15K rpm SAS , Total 16, Size of test database: 1000G Data Storage Ratio: Database Load Mechanism Details and Illustration The details of the database load must be disclosed, including a block diagram illustrating the overall process. Disclosure of the load procedure includes all steps, scripts, input and configuration files required to completely reproduce the test and qualification databases. Flat files for each of the tables were created using DBGEN. The tables were loaded as depicted in Figure

21 Create Flat Files for each table Create Database Configure Database for load Partitioned Load from Flat Files Create Indices and Constraints Timed Load Create Statistics and set date correlation Create RFs, backup DB End of Load Figure 5.8: Block Diagram of Database Load Process 5.9 Qualification Database Configuration The details of the database load must be disclosed, including a block diagram illustrating the overall process. Disclosure of the load procedure includes all steps, scripts, input and configuration files required to completely reproduce the test and qualification databases. The qualification database used identical scripts to create and load the data with changes to adjust for the database scale factor Dataset Verification Verify that the rows in the loaded database after the performance test are correct by comparing some small number of rows extracted at random from any two files of the corresponding Base, Insert and Delete reference data set files for each table and the corresponding rows of the database. Verified according to the specification. 21

22 6.0 Clause 5: Performance Metrics and Execution Rules Related Items 6.1 Steps after the Load Test Any system activity on the SUT that takes place between the conclusion of the load test and the beginning of the performance test must be fully disclosed including listings of scripts or command logs. Auditor requested queries were run against the database to verify the correctness of the load. The system was rebooted and SQL Server was restarted. 6.2 Steps in the Power Test The details of the steps followed to implement the power test (e.g., system boot, database restart, etc.) must be disclosed. The following steps were used to implement the power test: 1. RF1 Refresh Transaction 2. Stream 0 Execution 3. RF2 Refresh Transaction. 6.3 Timing Intervals for Each Query and Refresh Function The timing intervals (see Clause 5.3.6) for each query of the measured set and for both refresh functions must be reported for the power test. The timing intervals for each query and both refresh functions are given in the Numerical Quantities Summary earlier in this document on page vi. 6.4 Number of Streams for The Throughput Test The number of execution streams used for the throughput test must be disclosed. 7 streams were used for the Throughput Test. 6.5 Start and End Date/Times for Each Query Stream The start time and finish time for each query execution stream must be reported for the throughput test. The Numerical Quantities Summary on page vi contains the start and stop times for the query execution streams run on the system reported. 6.6 Total Elapsed Time for the Measurement Interval The total elapsed time of the measurement interval(see Clause 5.3.5) must be reported for the throughput test. The Numerical Quantities Summary on page vi contains the timing intervals for the throughput test run on the system reported. 6.7 Refresh Function Start Date/Time and Finish Date/Time Start and finish time for each update function in the update stream must be reported for the throughput test. The Numerical Quantities Summary on page vi contains the start and finish times for the refresh functions of each stream. 22

23 6.8 Timing Intervals for Each Query and Each Refresh Function for Each Stream The timing intervals (see Clause 5.3.6) for each query of each stream and for each update function must be reported for the throughput test. The timing intervals for each query and each update function are given in the Numerical Quantities Summary earlier in this document on page vii. 6.9 Performance Metrics The computed performance metrics, related numerical quantities and the price performance metric must be reported. The Numerical Quantities Summary contains the performance metrics, related numerical quantities, and the price/performance metric for the system reported The Performance Metric and Numerical Quantities from Both Runs The performance metric and the numerical quantities (TPC-H and TPC-H Size) from both of the runs must be disclosed Run ID Run 1 98, , ,925.1 Run 2 95, , , System Activity Between Tests Any activity on the SUT that takes place between the conclusion of Run1 and the beginning of Run2 must be disclosed. Auditor requested queries were run against the database and the log was truncated. The system was rebooted and SQL Server restarted. 23

24 7.0 Clause 6: SUT and Driver Implementation Related Items 7.1 Driver A detailed description of how the driver performs its functions must be supplied, including any related source code or scripts. This description should allow an independent reconstruction of the driver. The TPC-H benchmark was implemented using a Microsoft tool called StepMaster. StepMaster is a general purpose test tool which can drive ODBC and shell commands. Within StepMaster, the user designs a workspace corresponding to the sequence of operations (or steps) to be executed. When the workspace is executed, StepMaster records information about the run into a database as well as a log file for later analysis. StepMaster provides a mechanism for creating parallel streams of execution. This is used in the throughput tests to drive the query and refresh streams. Each step is timed using a millisecond resolution timer. A timestamp T1 is taken before beginning the operation and a timestamp T2 is taken after completing the operation. These times are recorded in a database as well as a log file for later analysis. Two types of ODBC connections are supported. A dynamic connection is used to execute a single operation and is closed when the operation finishes. A static connection is held open until the run completes and may be used to execute more than one step. A connection (either static or dynamic) can only have one outstanding operation at any time. In TPC-H, static connections are used for the query streams in the power and throughput tests. StepMaster reads an Access database to determine the sequence of steps to execute. These commands are represented as the Implementation Specific Layer. StepMaster records its execution history, including all timings, in the Access database. Additionally, StepMaster writes a textual log file of execution for each run. The stream refresh functions were executed using multiple batch scripts. The initial script is invoked by StepMaster, subsequent scripts are called from within the scripts. The source code for StepMaster and the RF Scripts is disclosed on Appendix E/F 7.2 Implementation Specific Layer (ISL) If an implementation-specific layer is used, then a detailed description of how it performs its functions must be supplied, including any related source code or scripts. This description should allow an independent reconstruction of the implementation-specific layer. The following steps are performed, to accomplish the Power and Throughput Runs: 1. Power Run Execute 96 concurrent RF1 threads, each of which will apply a segment of a refresh set generated by DBGen. Each thread submits multiple transactions, where a transaction spans a set of orders and their associated line items. A checkpoint was issued after RF1 completion. Execute the Stream 0 queries in the order according to TPC Benchmark H Specification, Appendix A Execute 96 concurrent RF2 threads, each of which will apply a segment of a refresh set generated by DBGen. Each thread submits multiple transactions, where a transaction spans a set of orders and their associated line items. A checkpoint was issued after RF2 completion. 24

25 2. Throughput Run Execute 7 concurrent query streams. Each stream executes queries in the order according to TPC Benchmark H Specification, Appendix A, for the appropriate Stream ID (01-07). Upon completion of each stream, a semaphore is signaled to indicate completion. Execute 7 consecutive RF1/RF2 transactions, against ascending Refresh sets produced by DBGen. The first RF1 waits on a semaphore prior to beginning its insert operations. Each step during the query execution is timed by StepMaster. The timing information, together with an activity log, are stored for later analysis. The inputs and results of steps are stored in text files for later analysis. The StreamRF timings are kept in a Masterlog file. 7.3 Profile-Directed Optimization If profile-directed optimization as described in Clause is used, such use must be disclosed. Profile-directed optimization was not used. 25

26 8. Clause 7: Pricing Related Items 8.1 Hardware and Software Used A detailed list of hardware and software used in the priced system must be reported. Each item must have a vendor part number, description, and release/revision level, and indicate General Availability status or committed delivery date. If package pricing is used, contents of the package must be disclosed. Pricing source(s) and effective date(s) of price(s) must also be reported. The pricing summary sheet is given on page v in the Executive Summary at the front of this report. The source for all prices is indicated. The HP ProLiant DL785 G6, Disk controllers and hard drives are available at the time of publication. The pricing and availability of the Microsoft software used is given in a quote from Microsoft, which is included in this report in Appendix H. 8.2 Three-Year Cost of System Configuration The total 3-year price of the entire configuration must be reported, including: hardware, software, and maintenance charges. Separate component pricing is required. The pricing summary sheet on page v in the front of this report contains all details. 8.3 Availability Dates The committed delivery date for general availability (availability date) of products used in the priced calculations must be reported. When the priced system includes products with different availability dates, the single availability date reported on the first page of the executive summary must be the date by which all components are committed to being available. The full disclosure report must report availability dates individually for at least each of the categories for which a pricing subtotal must be provided (see Clause ). All availability dates, whether for individual components or for the SUT as a whole, must be disclosed to a precision of 1 day, but the precise format is left to the test sponsor. Category Server Hardware Storage Server Software SQL Server Available Now (date of publication) Now (date of publication) Now (date of publication) Now (date of publication) 26

27 9. Clause 8: Audit Related Items 9.1 Auditors Report The auditor s agency name, address, phone number, and Attestation letter with a brief audit summary report indicating compliance must be included in the full disclosure report. A statement should be included specifying who to contact in order to obtain further information regarding the audit process. This implementation of the TPC Benchmark H was audited by Lorna Livingtree of Performance Metrics, a certified TPC-H auditor. Further information regarding the audit process may be obtained from: Lorna Livingtree Performance Metrics Inc. PO Box 984 Klamath, CA (707) TPC Benchmark H Full Disclosure Report and other information can be downloaded from the Transaction Processing Performance Council web site at 27

28 28

29 29

30 Appendix A: Tunable Parameters System Info System Information report written at: 10/29/09 09:36:38 System Name: OCTANE1 [System Summary] Item Value OS Name Microsoft Windows Server 2008 R2 Enterprise Version Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name OCTANE1 System Manufacturer HP System Model ProLiant DL785 G6 System Type x64-based PC Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) Processor Six-Core AMD Opteron(tm) Processor 8439 SE, 2793 Mhz, 6 Core(s), 6 Logical Processor(s) BIOS Version/Date HP A15, 8/14/2009 SMBIOS Version 2.5 Windows Directory J:\Windows System Directory J:\Windows\system32 Boot Device\Device\HarddiskVolume62 Locale United States Hardware Abstraction Layer Version = " " User Name Not Available Time Zone Pacific Daylight Time Installed Physical Memory (RAM) 512 GB Total Physical Memory 512 GB Available Physical Memory 13.8 GB Total Virtual Memory 513 GB Available Virtual Memory 13.6 GB Page File Space 1.00 GB Page File J:\pagefile.sys [Hardware Resources] [Conflicts/Sharing] Resource Device Memory Address 0xFD xFDBFFFFF PCI bus Memory Address 0xFD xFDBFFFFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 I/O Port 0x x F Direct memory access controller I/O Port 0x x F PCI bus Memory Address 0xFDC xFDFFFFFF PCI bus Memory Address 0xFDC xFDFFFFFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 I/O Port 0x000003C0-0x000003DF PCI bus I/O Port 0x000003C0-0x000003DF Standard VGA Graphics Adapter IRQ 5 Standard OpenHCD USB Host Controller IRQ 5 Standard OpenHCD USB Host Controller IRQ 5 Standard Enhanced PCI to USB Host Controller Memory Address 0xE xFD5FFFFF PCI bus Memory Address 0xE xFD5FFFFF Standard VGA Graphics Adapter IRQ 11 IPMI Interface IRQ 11 Base System Device IRQ 11 Base System Device I/O Port 0x x0000FFFF PCI bus I/O Port 0x x0000FFFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 I/O Port 0x x00006FFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 I/O Port 0x x00006FFF PCI bus Memory Address 0xFD xFD7FFFFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 Memory Address 0xFD xFD7FFFFF PCI bus I/O Port 0x000000A0-0x000000A1 Programmable interrupt controller I/O Port 0x000000A0-0x000000A1 Motherboard resources Memory Address 0xA0000-0xBFFFF PCI bus 30 Memory Address 0xA0000-0xBFFFF Standard VGA Graphics Adapter I/O Port 0x x00008FFF PCI bus I/O Port 0x x00008FFF ServerWorks (Broadcom) HT-2100 HT-PCI-E Bridge 0 I/O Port 0x000003B0-0x000003BB PCI bus I/O Port 0x000003B0-0x000003BB Standard VGA Graphics Adapter I/O Port 0x x00005FFF PCI bus I/O Port 0x x00005FFF Standard VGA Graphics Adapter Memory Address 0xF xFBFFFFFF ServerWorks (Broadcom) HT-1000 HT-PCI-X Bridge 0 Memory Address 0xF xFBFFFFFF ServerWorks (Broadcom) HT-1000 HT-PCI-X Bridge Memory Address 0xF xFBFFFFFF Broadcom BCM5706C NetXtreme II GigE I/O Port 0x x F Extended IO Bus I/O Port 0x x F Motherboard resources I/O Port 0x x Programmable interrupt controller I/O Port 0x x Motherboard resources [DMA] Resource Channel 7 controller [Forced Hardware] Device PNP Device ID [I/O] Device Status Direct memory access OK Resource Device Status 0x x F Standard Universal PCI to USB Host Controller OK 0x x ATA Channel 1 OK 0x x ATA Channel 1 OK 0x x F Standard Dual Channel PCI IDE Controller OK 0x00000CA2-0x00000CA3 Microsoft Generic IPMI Compliant Device OK 0x x Programmable interrupt controller OK