TPC BenchmarkTM C Full Disclosure Report

Transcription

1 TPC BenchmarkTM C Full Disclosure Report Oracle's SPARC T5-8 Server Using Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning for Oracle Solaris. First Edition March 26, 23 TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23

2 First Printing March 26, 23 Copyright 23 Oracle and/or its affiliates. All rights reserved. Oracle, 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. The performance information in this document is for guidance only. System performance is highly dependent on many factors including system hardware, system and user software, and user application characteristics; relative system performance may vary significantly as a result of these and other factors. The Sponsor does not warrant or represent that a user can or will achieve similar performance. No warranty on system performance or price/performance is expressed or implied in this document. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS (c)()(ii) and FAR , Rights in Technical Data and Computer Software (October 988). The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THE PUBLICATION. ORACLE AMERICA, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME. TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 2

3 Abstract This report documents the methodology and results of the TPC Benchmark TM C test conducted on the following environment as measured by Oracle America, Inc. The benchmark configuration, environment and methodology used to produce and validate the test results, and the pricing model used to calculate the price/performance, were audited by Francois Raab of InfoSizing to verify compliance with the relevant TPC specifications. System Processors SPARC T5-8 Server 8 SPARC T5 3.6GHz Database Environment Operating System Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning Oracle Solaris. Price / Performance Availability Date TPC Benchmark C Metrics Total System Cost Three year cost includes: Hardware Software Maintenance $4,663,73 USD TPC-C Throughput Maximum Qualified Date for which all Throughput expressed as components, hardware Total System Cost / tpmc transactions per minute and software are available C (tpmc) for purchase 8,552,523 $.55 USD TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 September 25, 23 3

4 Executive Summary TPC-C 5.. TPC-Pricing.7. SPARC T5-8 Server Report Date March 26, 23 Total System Cost TPC-C Throughput Price/Performance Availability Date $4,663,73USD 8,552,523 tpmc $.55USD/tpmC September 25, 23 Database Server Processors/Cores/Threads Database Manager Operating System Other Software Number of Users SPARC T5 3.6GHz 8 / 28 /,24 Oracle Database g Release 2 Enterprise Edition With Oracle Partitioning Oracle Solaris. Oracle Tuxedo CFSR Oracle Web Tier 6,8, Database System Clients Storage 54 DATA COMSTAR 6 Sun Server X3-2 2 Intel Xeon E GHz 64GB Memory 2 6GB SAS disk Sun Server X3-2L w/ 2 Intel Xeon E GHz 6GB DDR3 46 w/ 3TB 7.2K RPM SAS 8 w/ 2 3TB 7.2K RPM SAS 4 F4 PCI-E 4GB SSD 2 REDO COMSTAR Sun Server X3-2L w/ 2 Intel Xeon E GHz 6GB DDR3 2 3TB 7.2K RPM SAS SPARC T5-8 Server 8 SPARC T5 3.6GHz 4TB Memory 2 6GB K RPM SAS 2 8Gb/s FC HBA, 2 port GbE SFP+ System Component Each Server Node Processors/Cores/Threads SPARC T5 3.6GHz 8/28/24 and cache 8MB L3 Cache Memory Each Client 2/6/32 4TB Intel Xeon E MB Smart Cache 64GB Disk Controllers 2 8Gb/s FC HBA 2 Port 8 port Internal SAS OS Disks (each system) 2 6GB K RPM SAS 2 6GB K RPM SAS 26 Flash Accelerator F4 PCI-E 4GB emlc 86 3TB 7.2K RPM SAS External Storage Total Storage 344.4TB

5 TPC-C 5.. TPC-Pricing.7. SPARC T5-8 Server Description Server Hardware Sun SPARC T5-8 Server, XATO chassis 2 SPARC T5 3.6GHz 32GB DDR3-66 registered DIMM 6GB K RPM 2.5 SAS-2 HDD w/ bracket StorageTek 8Gb/s FC HBA dual port Emulex Twinax Passive Copper Cable: 2 meters Power cord, 2.5M, C2 plug Part Number T SG-PCIE2FC-EM8-Z X23A-3M-N SELY9P3Z Price Source Unit Price Report Date March 26, 23 Extended Price Qty 43,62 33,856 3, , yr Maint. Price ,62 35,424 44,856,23 28, Sub-Total 65,458 Server Storage Sun Sun Server X3-2L; base chassis Oracle Solaris. Preinstall 6GB K rpm 2.5 SAS-2 HDD w/ bracket 3TB 7.2K RPM 3.5 SAS HDD w/ bracket Intel Xeon E GHz Processor 8GB DDR3-6 DIMM StorageTek 8Gb/s FC PCI-E HBA dual port QLogic Sun Storage 6Gb/s SAS PCI-E HBA, Internal: 8 port Sun Storage 6Gb/s SAS PCI-E HBA, 52MB, RAID Flash Accelerator F4 PCI-E 4GB emlc Heat Sink (for factory installation) 2 LFF slot disk cage and 2 SFF rear slot disk cage Power Cord North America and Asia, 2.5M, 5-5P 5M LC-LC FC Optical Cable RA-SS2CF-6GK SG-PCIE2FC-QF8-Z SG-SAS6-INT-Z SGX-SAS6-R-INT-Z A-25-5-NEMA 9734A-Z-N 3, ,399 49,79 4,86 28, ,472 68,88 77,83 57,792 7,24 39,42 22,626 2,58,49,76 3,36 78,736,456 9,3 Sub-Total,74,42 Server Software Oracle Solaris. Preinstall 7422 Oracle Database g Release 2 Enterprise Edition, Per Processor for 3 years (for 64 processors) Oracle Partitioning, Per Processor for 3 years (for 64 processors) Oracle Incident Server Support Package (for 3 years) 23,75 5,75 2, ,52, 368, Sub-Total,888, 6,9 6,9 Client Hardware Sun Server X3-2; base chassis 6GB K RPM 2.5 SAS HDD w/ bracket Intel Xeon E core 2.9GHz Processor Sun Storage 6Gb/s SAS PCI-E HBA, Internal: 8 port Four 2.5 drive slots and DVD-RW disk cage Twinax Passive Copper Cable: 3 Meters Heatsink (for factory installation) PCI-E filler panel (for factory installation) Power Cord North America and Asia, 2.5M, 5-5P plug 8GB DDR3-6 DIMM RA-SS2CF-6GK SG-SAS6-INT-Z 7274 X23A-3M-N A-25-5-NEMA 773 3, , ,26 9,68 9,54 6,74,86 3, ,456 Sub-Total 29,92 Client Software Oracle Solaris. Preinstall 7734 Oracle Solaris Development Tools Support B5932 Oracle Web Tier, per Processor for 3 years (for 28 processors) Oracle Premier Software Support for Oracle Web Tier (for 28 processors) Oracle Tuxedo CFSR, per Processor for 3 years (for 28 processors) Oracle Premier Support for Oracle Tuxedo CFSR (for 28 processors),2 2,5 4,8,8 5, Sub-Total 32, 23, X333V-2-5-C4-N , , ,4 52,64 55,4 Other Hardware Brocade 65 FC Switch w/ 24 ports activated Rack Jmpr Cbl, Straight 2.M,C4,5A,C3 Brocade 65 ActivationPermit for 2 8Gb/s SFPs Brocade 6Gb/s SFP short wave optic module Rack rail kit 3,6 52,92 5,964 37, ,64

6 Part Number Description Price Source SUT Mgmt system and Svc Processor Control Workstation Sun Server X3-2; base chassis Oracle Solaris. Preinstall 7734 US PC Peripheral Kit (Keyboard / Mouse) X37A-PC 8GB DDR3-6 DIMM 773 Sun Storage 6Gb/s SAS PCI-E HBA, internal: 8 port SG-SAS6-INT-Z Four 2.5 drive slots and DVD-RW disk cage 7274 Heatsink (for factory installation) PCI-E filler panel (for factory installation) Single processor I/O cover kit (for factory installation) 749 Power Cord North America and Asia, 2.5M,5-5P plug 333A-25-5-NEMA Intel Xeon E GHz (for factory installation) 764 3GB K RPM 2.5 SAS HDD w/ bracket RB-SS2CF-3GK2 Sun Rack II 42U SR-242E-N PDU 5kVA, Single Phase, LV SR-5K-L63-N Jumper Cable Kit SunRack II SF-JUMPKIT-N 2M LC to LC FC Optical Cable X9732A-Z-N Acer V83HVAb 8 LCD Extreme Networks Summit X65-24t Netgear ProSafe Plus JGS524E 24 port (+%) C2G 25' Red Cat5e cable (+%) Oracle Premier Hardware Support Q-PREM-SPRT-SYS Unit Price 3, ,849, , Total Oracle Hardware, Software and Maintenance Discount Pricing Sources:. Oracle 2. CDW Audited by Francois Raab of InfoSizing, Inc. Notes: These components are not immediately orderable. See the FDR for more information. 3 yr Maint. Price , ,396 9, ,44, Sub-Total 89,66,36 5,24,436,597, ,76 Totals Extended Price Qty 3,36,,8 (2,24,76) Three-Year Cost of Ownership: tpmc $/tpmc $4,663,73 8,552, USD 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 section of the TPC benchmark specifications. If you find that stated prices are not available according to these terms, please inform the TPC at pricing@tpc.org. Thank you.

7 TPC-C 5.. TPC-Pricing.7. SPARC T5-8 Server Report Date March 26, 23 Numerical Quantities Summary: MQTh, computed Maximum Qualified Throughput Response Time in Seconds 8,552,523 9th % Avg. Max. New-Order Payment Order-Status Delivery (Interactive) Delivery (Deferred) Stock-Level Menu Response Time delay added for emulated components. Transaction Mix, in percent of total transactions New-Order 44.96% Payment 43.% Order-Status 4.% Delivery 4.% Stock-Level 4.% Keying / Think Times (in seconds) New-Order Min. Avg. Max Payment Order-Status Delivery Stock-Level Test Duration Ramp-up Time 3,84 seconds Measurement Interval 7,2 seconds Number of Checkpoints Checkpoint Interval Number of transactions (all types) completed in Measurement Interval 4 Minimum,722 seconds 2,282,77,

8 Benchmark Sponsor: Brad Carlile Sr. Director, Strategic Applications Engineering (SAE) Oracle Corporation 3295 NW 2th Terrace Hillsboro OR 9724 March 2, 22 I verified the TPC Benchmark C performance of the following Client Server configuration: Platform: SPARC T5-8 Server Operating system: Oracle Solaris. Database Manager: Oracle Database g Release 2 Enterprise Edition w/ Oracle Partitioning Transaction Manager: Oracle Tuxedo CFSR The results were: CPU's Speed Memory Disks New-Order 9% RT tpmc 8 x SPARC T5 4 TB 2 x 6 GB K rpm SAS 26 x 4 GB SSD 86 x 3 TB 7.2K rpm SAS.4 Sec. 8,552,523.4 (3.6 GHz) (8 MB Cache per processor) Sixteen (6) Clients: Sun Server X3-2 (each with) 2 x Intel Xeon E5-269 (2.93 GHz) 64 GB (2 MB Smart Cache per processor) 2 x 6 GB K rpm SAS n/a n/a In my opinion, these performance results were produced in compliance with the TPC requirements for the benchmark.

9 The following verification items were given special attention: The transactions were correctly implemented The database records were the proper size The database was properly scaled and populated The ACID properties were met Input data was generated according to the specified percentages The transaction cycle times included the required keying and think times The reported response times were correctly measured At least 9% of all delivery transactions met the 8 Second completion time limit All 9% response times were under the specified maximums The measurement interval was representative of steady state conditions The reported measurement interval was 2 minutes, seconds Log-switch initiated checkpoints were used during the measurement interval The 6 day storage requirement was correctly computed The system pricing was verified for major components and maintenance Additional Audit Notes: None. Respectfully Yours, François Raab, President

10 Table of Contents TPC Benchmark C Metrics... 3 Introduction...7 General Items...8. Application Code and Definition Statements Sponsor Parameter Settings Configuration Diagrams...8 Clause : Logical Database Design Related Items Table Definitions Physical Organization of Database Insert and Delete Operations Partitioning...23 Clause 2: Transaction And Terminal Profiles Related Items Random Number Generation Input/Output Screen Layouts Terminal Feature Verification Presentation Manager or Intelligent Terminal Percentage of Home and Remote Order-lines Percentage of Rolled Back New-Orders Items per New-Order Percentage of Home and Remote Payments Percentage of Access by Last Name Percentage of Skipped Deliveries Transaction Mix Queueing Mechanism Clause 3 Transaction and System Properties Related Items Transaction System Properties (ACID) Atomicity Completed Transaction Aborted Transaction Consistency Isolation Tests Isolation Test Isolation Test Isolation Test Isolation Test Isolation Test Isolation Test Isolation Test Isolation Test Isolation Test Durability Loss of Memory, Instantaneous Interruption, Power Loss, and Loss of Log Loss of Durable Media Containing Database Tables Clause 4: Scaling and Database Population Related Items Initial Cardinality of Tables Database Layout Type of Database Mapping of Database Day Space Computation...33 Clause 5: Performance Metrics and Response Time Related Items Measured tpmc Response Times Keying and Think Times Response Time Frequency Distribution Curves Think Time Frequency Distribution Response Times versus Throughput Throughput versus Elapsed Time Steady State Determination...38 TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23

11 5.9 Work Performed During Steady State Measurement Period Duration Transaction Mix Regulation Transaction Mix Percentage of New-Order Transactions Number of Order-lines per New-Order Percentage of Remote Order-lines per New-Order Percentage of Remote Payments Percentage of Non-Primary access by C_LAST for Payment and Order-Status Percentage of Skipped Delivery Transactions Checkpoints Clause 6: SUT, Driver and Communications Related Items RTE Description Lost Connections Emulated Components Configuration Diagrams Network Configuration Operator Intervention Clause 7: Pricing Related Items Hardware and Software Component Pricing Total Three Year Cost Availability Hardware and Software Support Statement of tpmc, Price/Performance Country Specific Pricing Orderability Date Clause 8: Audit Related Items Auditor's Report Appendix A: Application Source Client Source Code tpccclient.c...45 tpccclient.h...45 tpcctux.c tpcctux.h tpccdiag.c...47 tpccdiag.h...47 tpccnsapi.c tpccservice.c...49 tpccservice.h tpccbool.h...59 tpccconst.h tpccdata.h...59 tpcc.h Multi_svr...6 ora_errrpt.c... 6 ora_err.h...6 tpcc_srv_del.c...6 tpcc_srv_init.c tpcc_srv_util.c ora_oci.h tpccflags.h...66 tpcc.h Uni_svr...69 ora_errrpt.c tpcc_srv_init.c tpcc_srv_newo.c... 7 tpcc_srv_ords.c...73 tpcc_srv_paym.c...76 tpcc_srv_stock.c tpcc_srv_util.c Stored Procedures... 8 TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23

12 paynz.sql...8 payz.sql...8 tkvcpdel.sql...8 tpvcpnew.sql... 8 Appendix B: Database Build analyze.sql createdb.sql...84 createindex_icust.sql createindex_icust2.sql createindex_idist.sql createindex_iitem.sql...84 createindex_inord.sql createindex_iordl.sql createindex_iordr.sql createindex_iordr2.sql createindex_istok.sql createindex_iware.sql createspacestats.sql...85 createstoredprocs.sql createtable_cust.sql...85 createtable_dist.sql createtable_hist.sql createtable_item.sql...86 createtable_nord.sql...86 createtable_ordl.sql...86 createtable_ordr.sql...86 createtable_stok.sql createtable_ware.sql createts.sh loadcust.sh loaddist.sh...92 loadhist.sh...92 loaditem.sh loadnord.sh loadordrordl.sh... loadstok.sh...7 loadware.sh... p_build.ora... p_create.ora... 2 space_get.sql...2 space_init.sql... 2 space_rpt.sql... 2 tkvcinin.sql... 3 tpccload.c...7 RTE Parameters...27 config...27 Appendix C: Parameter Settings...28 Oracle Data-Base Parameters...28 p_run.ora...28 listener.ora tnsnames.ora Sun Server T5-8 Parameters...28 uname pkg info entire /etc/release prtdiag...28 prtconf /etc/project /etc/system /etc/user_attr sd.conf TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 2

13 ssd.conf...53 interrupts.sh Oracle DBMS Version...54 /etc/vfstab /etc/hosts...54 format emlxs.conf... 8 fp.conf...83 mpt.conf...83 ses.conf psrset...83 COMSTAR DATA Heads...83 Measured and Priced COMSTAR DATA head (X3-2L) uname pkg info entire prtdiag...84 prtconf format Format for sample FMod...85 /etc/system mpt.conf...85 qlt.conf...85 sbdadm...86 metastat...86 COMSTAR REDO Heads...87 Priced and Measured COMSTAR REDO Head (X3-2L)...87 uname pkg info entire prtdiag...87 prtconf format /etc/vfstab /etc/system mpt.conf...88 /etc/project niwot.conf...89 qlt.conf...89 sbdadm...89 metastat...89 Clients... 9 prtdiag...9 prtconf... 9 format... 9 /etc/release... 9 pkg info entire... 9 /etc/vfstab... 9 /etc/hosts...9 /etc/system /etc/project /etc/user_attr ubbconfig...92 Brocade 53 SAN Switch TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 3

14 List of Figures Figure : REDO Log Example... 2 Figure 2: Measured Configuration...22 Figure 3: Database Mapping...33 Figure 4: 6 Day Space Calculations...33 Figure 5: New-Order Response Time Distribution...34 Figure 6: Payment Response Time Distribution...35 Figure 7: Order-Status Response Time Distribution Figure 8: Delivery (Interactive) Response Time Distribution Figure 9: Stock-Level Response Time Distribution Figure : New-Order Think Time Distribution Figure : New-Order Response Time versus Throughput Figure 2: New-Order Throughput versus Time TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 4

15 List of Tables Table : T5-8 Server Configuration...8 Table 2: DATA COMSTAR Configuration...9 Table 3: REDO COMSTAR Configuration... 2 Table 4: Client Configuration... 2 Table 5: Transaction Input Percentages and Mix...25 Table 6: Table Cardinality...3 Table 7: RTE Parameter Input... 4 Table 8: Statement of tpmc and Price/Performance...42 Table 9: Orderability Dates...43 TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 5

16 Preface This report documents the compliance of the Oracle TPC Benchmark TM C testing on the SPARC T5-8 Server running Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning, executing the TPC Benchmark TM C Standard, Revision 5... The TPC Benchmark TM C Full Disclosure Report is organized as follows: The main body of the document lists each item in Clause 8 of the TPC Benchmark TM C Standard and explains how each specification is satisfied. Appendix A contains the application source code that implements the Oracle Tuxedo CFSR transaction server code and Oracle Web Tier plug-ins. Appendix B contains the code used to create and load the database. Appendix C contains the configuration information for the Oracle Solaris., Oracle Web Tier, Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning and Oracle Tuxedo CFSR. TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 6

17 SPARC T5-8 Server TPC Benchmark TMC Full Disclosure Introduction The TPC Benchmark TM C Standard Specification requires test sponsors to publish, and make available to the public, a full disclosure report for the results to be considered compliant with the Standard. This report is intended to satisfy the Standard's requirement for full disclosure. It documents the compliance of the benchmark tests required in the TPC Benchmark TM C results for the SPARC T5-8 Server running Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning. In the Standard Specification, the main headings in Clause 8 are keyed to the other clauses. The headings in this report use the same sequence, so that they correspond to the titles or subjects referred to in Clause 8. Each section in this report begins with the text of the corresponding item from Clause 8 of the Standard Specification, printed in italic type. The plain type text that follows explains how the tests comply with the TPC-C Benchmark TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 7

18 . General Items Application Code and Definition Statements The application program (as defined in Clause 2..7) must be disclosed. This includes, but is not limited to, the code implementing the five transactions and the terminal input and output functions. Appendix A contains the application source code that implements the transactions and forms modules..2 Sponsor A statement identifying the benchmark sponsor(s) and other participating companies must be provided. This benchmark test was sponsored by Oracle America, Inc..3 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 but not limited to: Database tuning options Recovery/commit options Consistency/locking options Operating system and application configuration parameters Appendix C contains all the required parameter settings for the SPARC T5-8 Server database system, the Sun Server X3-2L COMSTAR heads, the Brocade 65 SAN switches, the Sun Server X3-2 clients, all Oracle Solaris. tunables, along with parameters for Oracle Database g Release 2 Enterprise Edition with Oracle Partitioning, Oracle Web Tier and Oracle Tuxedo CFSR..4 Configuration Diagrams Diagrams of both measured and priced configurations must be provided, accompanied by a description of the differences. Database System Description The SUT is a SPARC T5-8 Server running Oracle Database g Release 2 Enterprise Edition and Oracle Solaris.. The SPARC T5-8 Server is configured as described below: SPARC T5-8 Server Processors Processors / Cores / Threads 8 SPARC T5 3.6GHz 8 / 28 / 24 Memory 4 TB DDR3-66 Registered Disks 2 6GB K RPM 2.5 SAS Adapters Networks 2 StorageTek 8Gb/s FC PCI-E HBA dual port, Emulex Sun Storage 6Gb/s SAS PCI-E HBA Internal 4 port GbE integrated Ethernet Service Processor Integrated Table : T5-8 Server Configuration The Oracle Database g Release 2 Enterprise Edition database tables, indexes, and logs are accessed through two separate storage environments. For descriptive purposes the storage environments are labeled as DATA and REDO. All of the TPCC database objects, including tables, indexes, and temp storage is located in the DATA COMSTAR heads storage environment described in detail below in the DATA COMSTAR Heads Description section. The REDO COMSTAR heads storage environment is used solely for the Oracle Database g Release 2 Enterprise Edition redo logs and is described in detail in the REDO COMSTAR Heads Description (Logs) section. The SPARC T5-8 Server DBMS system is connected to the two Brocade 65 switches via 8 of the 2 8Gb/s PCI-E adapters. The remaining 4 8Gb/s PCI-E adapters are directly connected to the REDO COMSTAR heads. TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 8

19 DATA COMSTAR Heads Description The measured configuration of the DATA SAN consists of 54 Sun Server X3-2L's running Oracle Solaris. as Common Multi-protocol SCSI Target (COMSTAR) heads. The COMSTAR heads are configured and used as external storage controllers. Each of DATA COMSTAR heads were configured with the same hardware peripherals, version of Oracle Solaris., and were loaded with the distribution of database tables and indexes as detailed in the Mapping of Database section. The configuration of the Sun Server X3-2L is noted below. Sun Server X3-2L (Measured and Priced) Processor Intel Xeon E GHz Processors / Cores / Threads Memory Disks 2 / 8 / 6 6GB DDR Sun Server X3-2L w/ 3TB SAS K RPM 8 Sun Server X3-2L w/ 2 3TB SAS K RPM 2 6GB SAS 2.5 K RPM (mirrored boot disks) StorageTek 8Gb/s FC PCI-E HBA dual port, QLogic Adapters 4 Flash Accelerator F4 PCI-E 4GB emlc Sun Storage 6Gb/s SAS PCI-E HBA Internal Network 4 port GbE integrated Ethernet Service Processor Integrated Table 2: DATA COMSTAR Configuration Each DATA COMSTAR head is configured with 4 Flash Accelerator F4 PCI-E 4GB emlc internal HBA's. Each F4 HBA is configured with 4 GB FMODS (Flash Modules), 4 Flash Accelerator F4 PCI-E 4GB emlc HBA's are 6 FMODS for a total of.6tb per DATA COMSTAR. Each of the 4 Flash Accelerator F4 PCI-E 4GB emlc's is installed internally to the Sun Server X3-2L. Each FMOD is visible to the COMSTAR head as a separate device for a total of 6 devices per DATA COMSTAR head. Multiple logical units (LUNs) are striped across the 6 FMODs using Solaris Volume Manager (SVM). These LUNs are then exported and are visible to the SPARC T5-8 Server via the two Brocade 65 SAN switches across the 8Gb/s FC-AL. Half of the 54 DATA COMSTAR nodes are attached to the first SAN switch, with the other half attached to the second SAN switch. All 54 COMSTAR heads of the DATA SAN have 2 6GB SAS mirrored disks for Oracle Solaris. and 46 have 3TB SAS disk, while the remaining 8 have 2 3TB SAS disks, for a total of 6 3TB SAS disks, to satisfy the 6 day space requirements. No database tables were stored on the 3TB disks for the measurement, they were used solely for backup of the initial database and for 6 day storage. Each DATA COMSTAR head is connected to one of the two Brocade 65 SAN switches via an 8Gb/s fibre channel connection. REDO COMSTAR Heads Description (Logs) The configuration of the REDO COMSTAR heads consists of 2 Sun Server X3-2L's running Oracle Solaris. as Common Multi-protocol SCSI Target (COMSTAR) heads. The COMSTAR heads are configured and used as external storage controllers. Each of the REDO COMSTAR heads is configured with the same hardware peripherals, version of Oracle Solaris., and managed the same load for the Oracle redo (recovery) logs. The details of the Sun Server X3-2L's configuration is detailed below: TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 9

20 Sun Server X3-2L (Measured and Priced) Processor Intel Xeon E GHz Processors / Cores / Threads Memory Disks Adapters Network 2 / 8 / 6 6GB DDR TB SAS K RPM 2 6GB SAS 2.5 5K RPM (mirrored boot disks) 2 StorageTek 8Gb/s FC PCI-E HBA dual port, QLogic Sun Storage 6Gb/s SAS PCI-E HBA, 52MB, RAID 4 port GbE integrated Ethernet Service Processor Integrated Table 3: REDO COMSTAR Configuration Each REDO COMSTAR is configured with 2 3TB SAS disks using the 6Gb/s Internal SAS RAID adapter. Two 6GB drives are dedicated for the OS and local filesystems. The 2 3TB disks are configured as a 2 way RAID- stripe using the hardware RAID facility on the internal SAS PCI-E RAID HBA. 2 raw partitions are created and exported to the SPARC T5-8 Server via the directly attached 8Gb/s fibres. The following diagram is an example of how the SPARC T5-8 Server database is connected to the REDO COMSTAR heads to provide redundancy and continued access to the database redo (recovery) logs. The SPARC T5-8 Server database mirrors the redo logs to separate REDO COMSTAR heads. SPARC T5-8 Server 4x 8Gb/s Sun Server X3-2L REDO COMSTAR 4x 8Gb/s Figure : REDO Log Example Client Configuration Description The TPC-C transactions are entered via a Remote Terminal Emulator which communicates with Oracle Web Tier running on 6 Sun Server X3-2 clients. Each client is configured with: TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 2

21 Sun Server X3-2 Clients Processor Intel Xeon E GHz Processors / Cores / Threads Memory Disks 2 / 6 / GB DDR GB 5K RPM 2.5 SAS Adapters Sun Storage 6Gb/s SAS PCI-E HBA Internal Network 4 port GbE integrated Ethernet Service Processor Integrated Table 4: Client Configuration The client systems receive transactions via Oracle Web Tier which communicates with Oracle Tuxedo CFSR with connections into the Oracle Database g Release 2 Enterprise Edition. Figure 2: Measured Configuration shows the measured and priced configuration for the SPARC T5-8 Server TPC-C configuration. TPC Benchmark C Full Disclosure Report Oracle America, Inc. 23 2

22 Measured and Priced Configuration RTE SUT Mgmt System Sun Server X3-2 8 TFT Monitor Not Priced Clients 6 Sun Server X3-2 2 E GHz 64GB memory 2 6GB SAS SUT Mgmt Network GbE Connections to T5-8, X3-2, X3-2L, SAN Switches SPARC T5-8 Server 8 SPARC T5 3.6GHz 4TB DDR3 2 8Gb/s FC-AL 2 6GB SAS disks Client Network: Summit X65-24t GbE Switch Gbs 8 Gbs FC-AL 8x 8Gb/s 8x 8Gb/s 2 COMSTAR REDO LOGS Sun Server X3-2L 2 E GHz 6GB DDR3 2 3TB SAS disks PCI-E 52MB RAID SAS 2 8Gb/s PCI-E FC-AL 54 COMSTAR DATA Sun Server X3-2L 2 E GHz 6GB DDR3 46 w/ 3TB SAS disks 8 w/ 2 3TB SAS disks 4 Flash Accelerator F4 8Gb/s PCI-E FC-AL Brocade 65 2 X 48 port 8Gb/s blades Figure 2: Measured Configuration TPC Benchmark C Full Disclosure Report Oracle America, Inc

23 . Clause : Logical Database Design Related Items Table Definitions Listing must be provided for all table definition statements and all other statements used to set up the database. Appendix B describes the programs that define, create, and populate the Oracle database used for this testing..2 Physical Organization of Database The physical organization of tables and indices, within the database, must be disclosed. The details of the physical organization of the database tables and indices are described in the Mapping of Database section of this report on page 3. Each tablespace is mapped to a soft partition as exported by Solaris Volume Manager (SVM) from the DATA and REDO COMSTAR heads as described above in the DATA COMSTAR Heads Description on page 9 and the REDO COMSTAR Heads Description (Logs) on page 9. The full details of the scripts used to create the slices and partitions are in Appendix B..3 Insert and Delete Operations It must be ascertained that insert and/or delete operations to any of the tables can occur concurrently with the TPC-C transaction mix. Furthermore, any restrictions in the SUT database implementation that precludes inserts beyond the limits defined in Clause.4. must be disclosed. This includes the maximum number of rows that can be inserted and the maximum key value for these new rows. All insert and delete functions were verified and fully operational during the entire benchmark..4 Partitioning While there are a few restrictions placed upon horizontal or vertical partitioning of tables and rows in the TPC-C benchmark (see Clause.6), any such partitioning must be disclosed. The STOCK, HISTORY, ORDERS and ORDERLINE tables and their related indexes, are partitioned horizontally. The details of the partitioning are disclosed in Appendix B for the database build environment. TPC Benchmark C Full Disclosure Report Oracle America, Inc

24 2 2. Clause 2: Transaction And Terminal Profiles Related Items Random Number Generation The method of verification for the random number generation must be described. The Random Number Generator used was SysVr4 nrand48() and erand48() UNIX calls. 2.2 Input/Output Screen Layouts The actual layout of the terminal input/output screens must be disclosed. All screen layouts followed the specification exactly. The HTML source code used to generate the screens is available in Appendix A. 2.3 Terminal Feature Verification The method used to verify that the emulated terminals provide all the features described in Clause must be explained. The terminal attributes were verified by the auditor manually exercising each specification during the onsite audit portion of this benchmark. 2.4 Presentation Manager or Intelligent Terminal Any usage of presentation managers or intelligent terminals must be explained. Application code running on the client machines implemented the TPC-C user interface. No presentation manager software or intelligent terminal features were used. The data is passed to the terminals using the HTML format, which can be displayed with any standard Web browser. The application code for the HTML display generation is listed in Appendix A. 2.5 Percentage of Home and Remote Order-lines The percentage of home and remote order-lines in the New-Order transactions must be disclosed. The Transaction Input Percentages and Mix Table contains the percentage of home and remote order-lines for all of the New-Order transactions completed during the measurement interval. 2.6 Percentage of Rolled Back New-Orders The percentage of New-Order transactions that were rolled back as a result of an unused item number must be disclosed. The Transaction Input Percentages and Mix table contains the percentage of New-Order transactions that were rolled back due to an illegal item being entered. 2.7 Items per New-Order The number of items per orders entered by New-Order transactions must be disclosed. The Transaction Input Percentages and Mix table contains the average number of items ordered for each New-Order transaction. 2.8 Percentage of Home and Remote Payments The percentage of home and remote Payment transactions must be disclosed. The Transaction Input Percentages and Mix table contains the percentage of home and remote warehouse transactions that occurred during the measurement interval for the Payment transactions. 2.9 Percentage of Access by Last Name The percentage of Payment and Order-Status transactions that used non-primary key (C_LAST) access to the database must be disclosed. The Transaction Input Percentages and Mix table contains the percentage of Payment and Order-Status transactions that were accessed by C_LAST (non-primary key access) during the measurement interval. 2. Percentage of Skipped Deliveries The percentage of Delivery transactions that were skipped as a result of an insufficient number of rows in the NEWORDER table must be disclosed. The Transaction Input Percentages and Mix table contains the percentage of Delivery transactions which were skipped TPC Benchmark C Full Disclosure Report Oracle America, Inc

25 due to insufficient number of rows in the NEW-ORDER table. 2. Transaction Mix The mix (i.e., percentages) of transaction types seen by the SUT must be disclosed. The Transaction Input Percentages and Mix table contains the mix of each transaction type executed by the SUT. New-Order Percentage of Home order-lines SPARC T5-8 Server 99.% Percentage of Remote order-lines.% Percentage of Rolled Back Transactions.99% Avg. Number of Items per Transactions 9.99 Payment Percentage of Home Transactions 85.% Percentage of Remote Transactions 4.99% Access by C_LAST (Non-primary key) Percentage of Payment Transactions 59.99% Percentage of Order-Status Transactions 6.% Delivery Percentage of Deliveries skipped.% Transaction Mix New-Order 44.96% Payment 43.% Order-Status 4.% Delivery 4.% Stock-Level 4.% Table 5: Transaction Input Percentages and Mix 2.2 Queueing Mechanism The queueing mechanism used to defer the execution of the Delivery transaction must be disclosed. Delivery transactions were submitted to servers using the same mechanism that other transactions used, Tuxedo API. The only difference was that tpacall() was used instead of tpcall() to call the server process asynchronously, i.e. control would return to the client thread immediately and the deferred delivery part would complete asynchronously in the server process. TPC Benchmark C Full Disclosure Report Oracle America, Inc

26 3 3. Clause 3 Transaction and System Properties Related Items Transaction System Properties (ACID) The results of the ACID tests must be disclosed along with a description of how the ACID requirements were met. This includes disclosing which case was followed for the execution of Isolation Test 7. The TPC Benchmark C Standard Specification defines a set of transaction processing system properties that a system under test (SUT) must support during the execution of the benchmark. Those properties are Atomicity, Consistency, Isolation, and Durability (ACID). This section defines each of these properties, describes the steps taken to ensure that they were present during the test and describes a series of tests done to demonstrate compliance with the standard. 3.2 Atomicity The system under test must guarantee that transactions are atomic; the system will either perform all individual operations on the data, or will assure that no partially completed operations leave any effects on the data Completed Transaction Perform the Payment transaction for a randomly selected warehouse, district, and customer (by customer number as specified in Clause ) and verify that the records in the CUSTOMER, DISTRICT, and WAREHOUSE tables have been changed appropriately. A row was randomly selected from the warehouse, district and customer tables local to the database node running the transaction, and the balances noted. A payment transaction was started with the same warehouse, district and customer identifiers and a known amount. The payment transaction was committed and the rows were verified to contain correctly updated balances Aborted Transaction Perform the Payment transaction for a randomly selected warehouse, district, and customer (by customer number as specified in Clause ) and substitute a ROLLBACK of the transaction for the COMMIT of the transaction. Verify that the records in the CUSTOMER, DISTRICT, and WAREHOUSE tables have NOT been changed. A row was randomly selected from the warehouse, district and customer tables local to the database node running the transaction, and the balances noted. A payment transaction was started with the same warehouse, district and customer identifiers and a known amount. The payment transaction was rolled back and the rows were verified to contain the original balances Consistency Consistency is the property of the application that requires any execution of a database transaction to take the database from one consistent state to another, assuming that the database is initially in a consistent state. The benchmark specification requires explicit demonstration of the following four consistency conditions:. The sum of the district year-to-date (d_ytd) balance for all districts within a warehouse is equal to the balance of the warehouse year-to-date (w_ytd) for the district's warehouse; 2. For each district, the next order id (d_next_o_id) minus one, is equal to the most recent order id (max(o_id)) from the ORDER table for the associated district and warehouse. Also, the (d_next_o_id) minus one is equal to the max(no_o_id) (most recent new-order) from the NEW-ORDER table; 3. For each district, the maximum order id minus minimum order id in the ORDER table plus one equals the number of rows in the NEW-ORDER table for that district; 4. For each district, the sum of the order line counts in the ORDER table equals the number of rows in the ORDERLINE table for that district; These consistency conditions were tested using a shell script to issue queries to the database. The results of the queries verified that the database was consistent for all four tests. The same four consistency tests were performed after the reported performance run during the audit. 3.3 Isolation Tests The TPC Benchmark C Standard defines nine tests that are to be performed to demonstrate that required level of transaction isolation are met. TPC Benchmark C Full Disclosure Report Oracle America, Inc

27 3.3. Isolation Test. This test demonstrates isolation for read-write conflicts of Order-Status and New-Order transactions when the New-Order transaction is committed. The test proceeds as follows:. An Order-Status transaction T was executed and committed for a randomly selected customer, and the order returned was noted. 2. A New-Order transaction T was started for the same customer used in T. T was stopped prior to COMMIT. 3. An Order-Status transaction T2 was started for the same customer used in T. T2 completed and was committed without being blocked by T. T2 returned the same order that T had returned. 4. T was allowed to complete and was committed. 5. An Order-Status transaction T3 was started for the same customer used in T. T3 returned the order inserted by T Isolation Test 2 This test demonstrates isolation for read-write conflicts of Order-Status and New-Order transactions when the New-Order transaction is rolled back. The test proceeds as follows:. An Order-Status transaction T was executed and committed for a randomly selected customer and the order returned was noted. 2. A New-Order transaction T with an invalid item number was started for the same customer used in T. T was stopped immediately prior to ROLLBACK. 3. An Order-Status transaction T2 was started for the same customer used in T. T2 completed and was committed without being blocked by T. T2 returned the same order that T had returned. 4. T was allowed to ROLLBACK. 5. An Order-Status transaction T3 was started for the same customer used in T. T3 returned the same order that T had returned Isolation Test 3 This test demonstrates isolation for write-write conflicts of two New-Order transactions when both transactions are committed. The test proceeds as follows:. The D_NEXT_O_ID of a randomly selected district was retrieved. 2. A New-Order transaction T was started for a randomly selected customer within the district used in step. T was stopped immediately prior to COMMIT. 3. Another New-Order transaction T2 was started for the same customer used in T. T2 waited. 4. T was allowed to complete. T2 completed and was committed. 5. The order number returned by T was the same as the D_NEXT_O_ID retrieved in step. The order number returned by T2 was one greater than the order number returned by T. 6. The D_NEXT_O_ID of the same district was retrieved again. It had been incremented by two (i.e. it was one greater than the order number returned by T2) Isolation Test 4 This test demonstrates isolation for write-write conflicts of two New-Order transactions when one transaction is rolled back. The test proceeds as follows:. The D_NEXT_O_ID of a randomly selected district was retrieved. 2. A New-Order transaction T, with an invalid item number, was started for a randomly selected customer within the district used in step. T was stopped immediately prior to ROLLBACK. 3. Another New-Order transaction T2 was started for the same customer used in T. T2 waited. 4. T was allowed to roll back, and T2 completed and was committed. 5. The order number returned by T2 was the same as the D_NEXT_O_ID retrieved in step. 6. The D_NEXT_O_ID of the same district was retrieved again. It had been incremented by one (i.e. one greater than the order number returned by T2). TPC Benchmark C Full Disclosure Report Oracle America, Inc

28 3.3.5 Isolation Test 5 This test demonstrates isolation for write-write conflicts of Payment and Delivery transactions when Delivery transaction is committed. The test proceeds as follows:. A query was executed to find out the customer who is to be updated by the next delivery transaction for a randomly selected warehouse and district. 2. The C_BALANCE of the customer found in step was retrieved. 3. A Delivery transaction T was started for the same warehouse used in step. T was stopped immediately prior to COMMIT. 4. A Payment transaction T2 was started for the same customer found in step. T2 waited. 5. T was allowed to complete. T2 completed and was committed. 6. The C_BALANCE of the customer found in step was retrieved again. The C_BALANCE reflected the results of both T and T Isolation Test 6 This test demonstrates isolation for write-write conflicts of Payment and Delivery transactions when the Delivery transaction is rolled back. The test proceeds as follows:. A query was executed to find out the customer who is to be updated by the next delivery transaction for a randomly selected warehouse and district. 2. The C_BALANCE of the customer found in step was retrieved. 3. A Delivery transaction T was started for the same warehouse used in step. T was stopped immediately prior to ROLLBACK. 4. A Payment transaction T2 was started for the same customer found in step. T2 waited. 5. T was allowed to ROLLBACK. T2 completed and was committed. The C_BALANCE of the customer found in step was retrieved again. The C_BALANCE reflected the results of only T Isolation Test 7 This test demonstrates repeatable reads for the New-Order transaction while an interactive transaction updates the prices of some items. The test proceeds as follows:. The I_PRICE of two randomly selected items X and Y were retrieved. 2. A New-Order transaction T with a group of items including items X and Y was started. T was stopped immediately after retrieving the prices of all items. The prices of items X and Y retrieved matched those retrieved in step. 3. A transaction T2 was started to increase the price of items X and Y by %. 4. T2 did not stall and was committed. 5. T was resumed, and the prices of all items were retrieved again within T. The prices of items X and Y matched those retrieved in step. 6. T was committed. 7. The prices of items X and Y were retrieved again. The values matched the values set by T2. Execution followed Case D of Clause Isolation Test 8 This test demonstrates isolation for phantom protection between New-Order and Order-Status transactions. The test proceeds as follows:. An Order-Status transaction T was started for a randomly selected customer. 2. T was stopped immediately after reading the order table for the selected customer to find the most recent order for that customer. 3. A New-Order transaction T2 was started for the same customer. T2 completed and was committed without being blocked by T. 4. T was resumed and the ORDER table was read again to determine the most recent order for the same customer. The order found was the same as the one found in step T completed and was committed. TPC Benchmark C Full Disclosure Report Oracle America, Inc

29 3.3.9 Isolation Test 9. This test demonstrates isolation for phantom protection between New-Order and Delivery transactions. The test proceeds as follows:. The NO_D_ID of all NEW_ORDER rows for a randomly selected warehouse and district was changed to. The changes were committed. 2. A Delivery transaction T was started for the selected warehouse. 3. T was stopped immediately after reading the NEW_ORDER table for the selected warehouse and district. No qualifying row was found. 4. A New-Order transaction T2 was started for the same warehouse and district. T2 completed and was committed without being blocked by T. 5. T was resumed and the NEW_ORDER table was read again. No qualifying row was found. 6. T completed and was committed. 7. The NO_D_ID of all NEW_ORDER rows for the selected warehouse and district was restored to the original value. The changes were committed. 3.4 Durability 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 he failures listed in Clause Loss of Memory, Instantaneous Interruption, Power Loss, and Loss of Log This test was executed by following these steps:. The total number of orders was determined by the sum of D_NEXT_O_ID from all rows in the district table; giving the beginning count. 2. The RTE was started with full user load. 3. The test was allowed to ramp up and ran in steady state for more than 5 minutes. 4. A log switch checkpoint was initiated and completed. 5. The test ran for a least one more minute. 6. The power was removed to one of the REDO COMSTAR heads, thereby causing the loss of one-half of the mirrored log environment (loss of disk). Because the redo logs are mirrored across the REDO COMSTAR heads, the test continues to run without interruption. 7. The run continued for at least 5 minutes while maintaining steady state. 8. Power to the SPARC T5-8 Server was disconnected 9. The test was allowed to continue for at least one more minute. After minute, the RTE is interrupted and minutes later the Oracle Tuxedo CFSR servers and Oracle Web Tier servers were interrupted.. The power to the SPARC T5-8 Server is restored and the system is booted, the database is started and database recovery begins and completes.. Step was repeated, giving the ending count. 2. Consistency Test 3 was verified. 3. A sample from the success file was compared against the database. 4. The RTE report was used to determine the number of successful New-Order transactions. The difference between the counts in Steps and was compared with the RTE count to verify that no committed transactions were lost Loss of Durable Media Containing Database Tables This test can be executed on a small scaled database (at least %) under a reduced user load (at least %). The throughput is reaching at least % of the reported tpmc. When a reduced configuration is used, a target of 2% is recommended to avoid falling under the % threshold. This test was executed by following these steps:. The total number of orders was determined by the sum of D_NEXT_O_ID from all rows in the district table; giving the beginning count. 2. The RTE was started with a reduced terminal load to drive only 2% of the reported throughput. 3. The test was allowed to ramp up and ran in steady state for more than 5 minutes. 4. A checkpoint was manually initiated and completed. 5. The test was allowed to run for a least 5 more minutes. TPC Benchmark C Full Disclosure Report Oracle America, Inc