TPC BENCHMARK (TM) H (779138), страница 22

Просмтор этого файла доступен только зарегистрированным пользователям. Но у нас супер быстрая регистрация: достаточно только электронной почты!

Текст из файла (страница 22)

The data storage media must hold all the data described in Clause 4: and be attached to theprocessing units(s).TPC BenchmarkTM H Standard Specification Revision 2.17.1Page 1016.2.2All SUT components, as described in Clause 6.2.1, must be commercially available software or hardware products.6.2.3An implementation specific layer can be implemented on the SUT. This layer must be logically located between thedriver and the SUT, as depicted by Figure 4: Implementation Specific Layer.Figure 4: Implementation Specific LayerDRIVERExec. Query Text + Row CountOutput DataImplementation Specific LayerCommerc ially AvailableProducts(e.g., OS, DBMS, ISQL)SUT6.2.4An implementation specific layer, if present on the SUT, must be minimal, general purpose (i.e., not limited to theTPC-H queries) and its source code must be disclosed. Furthermore, the functions performed by an implementationspecific layer must be strictly limited to the following:Database transaction control operations before and after each query execution;Cursor control and manipulation operations around the executable query text;Definition of procedures and data structures required to process dynamic SQL, including thecommunication of the executable query text to the commercially available layers of the SUT and thereception of the query output data;Communication with the commercially available layers of the SUT;Buffering of the query output data;Communication with the driver.The following are examples of functions that the implementation specific layer shall not perform:Any modification of the executable query text;Any use of stored procedures to execute the queries;Any sorting or translation of the query output data;Any function prohibited by the requirements of Clause 5.2.7.6.3Driver Definition6.3.1The driver presents the workload to the SUT.6.3.2The driver is a logical entity that can be implemented using one or more programs, processes, or systems and perTPC BenchmarkTM H Standard Specification Revision 2.17.1Page 102forms the functions defined in Clause 6.3.3.6.3.3The driver can perform only the following functions:Generate a unique stream ID, starting with 1 (or 0 for the power test), for each query stream;Sequence queries for execution by the query streams (see Clause 5.3.5);Activate, schedule, and/or synchronize the execution of refresh functions in the refresh stream (see Clause5.3.7.8);Generate the executable query text for each query;Generate values for the substitution parameters of each query;Complete the executable query text by replacing the substitution parameters by the values generated forthem and, if needed, replacing the text-tokens by the query stream ID;Submit each complete executable query text to the SUT for execution, including the number of rows to bereturned when specified by the functional query definition;Submit each executable refresh function to the SUT for execution;Receive the output data resulting from each query execution from the SUT;Measure the execution times of the queries and the refresh functions and compute measurement statistics;Maintain an audit log of query text and query execution output.6.3.4The generation of executable query text used by the driver to submit queries to the SUT does not need to occur onthe SUT and does not have to be included in any timing interval.6.3.5The driver shall not perform any function other than those described in Clause 6.3.3.

Specifically, the driver shallnot perform any of the following functions:6.3.6Performing, activating, or synchronizing any operation other than those mentioned in Clause 6.3.3;Delaying the execution of any query after the execution of the previous query other than for delaysnecessary to process the functions described in Clause 6.3.3. This delay must be reported and cannotexceed half a second between any two consecutive queries of the same query stream;Modifying the compliant executable query text prior to its submission to the SUT;Embedding the executable query text within a stored procedure definition or an application program;Submitting to the SUT the values generated for the substitution parameters of a query other than as part ofthe executable query text submitted;Submitting to the SUT any data other than the instructions to execute the refresh functions, the compliantexecutable query text and, when specified by the functional query definition, the number of rows to bereturned;Artificially extending the execution time of any query.The driver is not required to be priced.TPC BenchmarkTM H Standard Specification Revision 2.17.1Page 1037: PRICINGThis section defines the components, functional requirements of what is priced, and what substitutions are allowed.Rules for pricing the Priced Configuration and associated software and maintenance are included in the TPCPricing Specification located at www.tpc.org.7.1Priced SystemThe system to be priced shall include the hardware and software components present in the System Under Test(SUT), a communication interface that can support user interface devices, additional operational components configured on the test system, and maintenance on all of the above7.1.1System Under TestCalculation of the priced system consists of:Price of the SUT as tested and defined in Clause 6: ;Price of a communication interface capable of supporting the required number of user interface devicesdefined in Clause 7.1.2.1;Price of on-line storage for the database as described in Clause 7.1.3 and storage for all software includedin the priced configuration;Price of additional products (software or hardware) required for customary operation, administration andmaintenance of the SUT for a period of 3 yearsPrice of all products required to create, execute, administer, and maintain the executable query texts ornecessary to create and populate the test database.Specifically excluded from the priced system calculation are:7.1.2End-user communication devices and related cables, connectors, and concentrators;Equipment and tools used exclusively in the production of the full disclosure report;Equipment and tools used exclusively for the execution of the DBGEN or QGEN (see Clause 4.2.1 andClause 2.1.4) programs.User Interface Devices and Communications7.1.2.1 The priced system must include the hardware and software components of a communication interface capable ofsupporting a number of user interface devices (e.g., terminals, workstations, PCs, etc.) at least equal to 10 times thenumber of query streams used for the throughput test (see 5.3.4.Comment: Test sponsors are encouraged to configure the SUT with a general-purpose communication interfacecapable of supporting a large number of user interface devices.7.1.2.2 Only the interface is to be priced.

Not to be included in the priced system are the user interface devices themselvesand the cables, connectors and concentrators used to connect the user interface devices to the SUT. For example, ina configuration that includes an Ethernet interface to communicate with PCs, the Ethernet card and supporting software must be priced, but not the Ethernet cables and the PCs.Comment: Active components (e.g., workstations, PCs, concentrators, etc.) can only be excluded from the pricedsystem under the assumption that their role is strictly limited to submitting executable query text and receiving output data and that they do not participate in the query execution.

All query processing performed by the tested configuration is considered part of the performance test and can only be done by components that are included in thepriced system.7.1.2.3 The communication interface used must be an industry standard interface, such as Ethernet, Token Ring, or RS232.7.1.2.4 The following diagram illustrates the boundary between what is priced (on the right) and what is not (on the left):TPC BenchmarkTM H Standard Specification Revision 2.17.1Page 104Figure 5: The Pricing BoundaryDriverSUT(Implementation Specific Layer)User InterfaceDevice(s)NetworkCommercially AvailableProducts(e.g., OS, DBMS, ISQL)Pricing Boundary7.1.3Database Storage and Recovery Log7.1.3.1 Recovery data must be maintained for at least the duration of the run used to compute the published performancemetrics (see Clause 5.1.1.3).Roll-back recovery data must be either in memory or in on-line storage at least until all transactions dependent on itare committed.

Roll-forward recovery data may be stored on an off-line device provided that:The process that stores the roll-forward data is active during the measurement interval;The roll-forward data that is stored off-line during the measurement interval must be at least as great as theroll-forward recovery data that is generated during the period (i.e., the data may be first created in on-linestorage and then moved to off-line storage, but the creation and the movement of the data must be in steadystate);All ACID properties must be retained.Comment: Storage is considered on-line if any record can be accessed randomly and updated within 1 second evenif this access time requires the creation of a logical access path not present in the tested database. For example, adisk-based sequential file might require the creation of an index to satisfy the access time requirement.

On-line storage may include magnetic disks, optical disks, or any combination of these, provided that the above mentionedaccess criteria are met.7.1.3.2 While the benchmark requires the configuration of storage sufficient to hold the requisite recovery data as specifiedin Clause 7.1.3.1, it does not explicitly require the demonstration of rollforward recovery except as required by theACID tests (See Clause 3.5).7.1.3.3 This clause has been left intentionally blank.7.1.3.4 The storage that is required to be priced includes:storage required to execute the benchmark;storage to hold recovery data (see Clause 7.1.3);storage and media needed to assure that the test database meets the ACID requirements defined in Clause 3:.7.1.3.5 All storage required for the priced system must be present on the tested system.7.1.4Additional Operational Components7.1.4.1 Additional products that might be included on a customer installed configuration, such as operator consoles andmagnetic tape drives, are also to be included in the priced system if explicitly required for the operation, administration, or maintenance, of the priced system.7.1.4.2 Copies of the software, on appropriate media, and a software load device, if required for initial load or maintenanceTPC BenchmarkTM H Standard Specification Revision 2.17.1Page 105updates, must be included.7.1.4.3 The price of an Uninterruptible Power Supply, if specifically contributing to a durability solution, must be included(see Clause 3.5.7.1.4.4 The price of all cables used to connect components of the system (except as noted in Clause 7.1.2.2) must beincluded.7.1.5Software7.1.5.1 All software licenses must be priced for a number of users at least equal to 10 times the number of query streamsused for the multi-stream throughput test (see Clause 5.3.4).

Характеристики

Список файлов книги