TPC BENCHMARK (TM) H (779138), страница 3
Текст из файла (страница 3)
In addition,this mix of queries and refresh functions is subject to specific ACIDity requirements, since queries andrefresh functions may execute concurrently;To achieve the optimal compromise between performance and operational requirements, the databaseadministrator can set, once and for all, the locking levels and the concurrent scheduling rules for queriesand refresh functions.The minimum database required to run the benchmark holds business data from 10,000 suppliers.
It contains almostten million rows representing a raw storage capacity of about 1 gigabyte. Compliant benchmark implementationsmay also use one of the larger permissible database populations (e.g., 100 gigabytes), as defined in Clause 4.1.3.The performance metric reported by TPC-H is called the TPC-H Composite Query-per-Hour Performance Metric(QphH@Size), and reflects multiple aspects of the capability of the system to process queries.
These aspects includethe selected database size against which the queries are executed, the query processing power when queries aresubmitted by a single stream and the query throughput when queries are submitted by multiple concurrent users. TheTPC-H Price/Performance metric is expressed as $/QphH@Size. To be compliant with the TPC-H standard, allreferences to TPC-H results for a given configuration must include all required reporting components (see ClauseTPC BenchmarkTM H Standard Specification Revision 2.17.1Page 85.4.6).
The TPC believes that comparisons of TPC-H results measured against different database sizes aremisleading and discourages such comparisons.The TPC-H database must be implemented using a commercially available database management system (DBMS)and the queries executed via an interface using dynamic SQL. The specification provides for variants of SQL, asimplementers are not required to have implemented a specific SQL standard in full.TPC-H uses terminology and metrics that are similar to other benchmarks, originated by the TPC and others. Suchsimilarity in terminology does not in any way imply that TPC-H results are comparable to other benchmarks. Theonly benchmark results comparable to TPC-H are other TPC-H results compliant with the same revision.Despite the fact that this benchmark offers a rich environment representative of many decision support systems, thisbenchmark does not reflect the entire range of decision support requirements.
In addition, the extent to which acustomer can achieve the results reported by a vendor is highly dependent on how closely TPC-H approximates thecustomer application. The relative performance of systems derived from this benchmark does not necessarily holdfor other workloads or environments.
Extrapolations to any other environment are not recommended.Benchmark results are highly dependent upon workload, specific application requirements, and systems design andimplementation. Relative system performance will vary as a result of these and other factors. Therefore, TPC-Hshould not be used as a substitute for a specific customer application benchmarking when critical capacity planningand/or product evaluation decisions are contemplated.Benchmark sponsors are permitted several possible system designs, provided that they adhere to the modeldescribed in Clause 6: .
A full disclosure report (FDR) of the implementation details, as specified in Clause 8, mustbe made available along with the reported results.Comment 1: While separated from the main text for readability, comments and appendices are a part of the standardand their provisions must be complied with.Comment 2: The contents of some appendices are provided in a machine readable format and are not included inthe printed copy of this document.0.2General Implementation GuidelinesThe rules for pricing are included in the TPC Pricing Specification located at www.tpc.org.The purpose of TPC benchmarks is to provide relevant, objective performance data to industry users. To achievethat purpose, TPC benchmark specifications require that benchmark tests be implemented with systems, products,technologies and pricing that:Are generally available to users;Are relevant to the market segment that the individual TPC benchmark models or represents (e.g., TPC-Hmodels and represents complex, high data volume, decision support environments);Would plausibly be implemented by a significant number of users in the market segment the benchmarkmodels or represents.The use of new systems, products, technologies (hardware or software) and pricing is encouraged so long as theymeet the requirements above.
Specifically prohibited are benchmark systems, products, technologies or pricing(hereafter referred to as "implementations") whose primary purpose is performance optimization of TPC benchmarkresults without any corresponding applicability to real-world applications and environments. In other words, all"benchmark special" implementations that improve benchmark results but not real-world performance or pricing, areprohibited.The following characteristics shall be used as a guide to judge whether a particular implementation is a benchmarkspecial. It is not required that each point below be met, but that the cumulative weight of the evidence be consideredto identify an unacceptable implementation. Absolute certainty or certainty beyond a reasonable doubt is notrequired to make a judgment on this complex issue.
The question that must be answered is: "Based on the availableTPC BenchmarkTM H Standard Specification Revision 2.17.1Page 9evidence, does the clear preponderance (the greater share or weight) of evidence indicate that this implementation isa benchmark special?"The following characteristics shall be used to judge whether a particular implementation is a benchmark special:a)Is the implementation generally available, externally documented, and supported?b)Does the implementation have significant restrictions on its use or applicability that limits its use beyondTPC benchmarks?c)Is the implementation or part of the implementation poorly integrated into the larger product?d)Does the implementation take special advantage of the limited nature of TPC benchmarks (e.g., queryprofiles, query mix, concurrency and/or contention, isolation requirements, etc.) in a manner that would notbe generally applicable to the environment the benchmark represents?e)Is the use of the implementation discouraged by the vendor? (This includes failing to promote theimplementation in a manner similar to other products and technologies.)f)Does the implementation require uncommon sophistication on the part of the end-user, programmer, orsystem administrator?g)Is the implementation (including beta) being purchased or used for applications in the market area thebenchmark represents? How many sites implemented it? How many end-users benefit from it? If theimplementation is not currently being purchased or used, is there any evidence to indicate that it will bepurchased or used by a significant number of end-user sites?Comment: The characteristics listed in this clause are not intended to include the driver or implementation specificlayer, which are not necessarily commercial software, and have their own specific requirements and limitationenumerated in Clause 6: .
The listed characteristics and prohibitions of Clause 6 should be used to determine if thedriver or implementation specific layer is a benchmark special.0.3General Measurement GuidelinesTPC benchmark results are expected to be accurate representations of system performance. Therefore, there arecertain guidelines that are expected to be followed when measuring those results. The approach or methodology tobe used in the measurements are either explicitly described in the specification or left to the discretion of the testsponsor.
When not described in the specification, the methodologies and approaches used must meet the followingrequirements:The approach is an accepted engineering practice or standard;The approach does not enhance the result;Equipment used in measuring the results is calibrated according to established quality standards;Fidelity and candor is maintained in reporting any anomalies in the results, even if not specified in the TPCbenchmark requirements.Comment: The use of new methodologies and approaches is encouraged so long as they meet the requirementsabove.TPC BenchmarkTM H Standard Specification Revision 2.17.1Page 101: LOGICAL DATABASE DESIGN1.1Business and Application EnvironmentTPC Benchmark™ H is comprised of a set of business queries designed to exercise system functionalities in amanner representative of complex business analysis applications.
These queries have been given a realistic context,portraying the activity of a wholesale supplier to help the reader relate intuitively to the components of thebenchmark.TPC-H does not represent the activity of any particular business segment, but rather any industry which mustmanage sell, or distribute a product worldwide (e.g., car rental, food distribution, parts, suppliers, etc.). TPC-H doesnot attempt to be a model of how to build an actual information analysis application.The purpose of this benchmark is to reduce the diversity of operations found in an information analysis application,while retaining the application's essential performance characteristics, namely: the level of system utilization and thecomplexity of operations.
A large number of queries of various types and complexities needs to be executed tocompletely manage a business analysis environment. Many of the queries are not of primary interest forperformance analysis because of the length of time the queries run, the system resources they use and the frequencyof their execution. The queries that have been selected exhibit the following characteristics:They have a high degree of complexity;They use a variety of accessThey are of an ad hoc nature;They examine a large percentage of the available data;They all differ from each other;They contain query parameters that change across query executions.These selected queries provide answers to the following classes of business analysis:Pricing and promotions;Supply and demand management;Profit and revenue management;Customer satisfaction study;Market share study;Shipping management.Although the emphasis is on information analysis, the benchmark recognizes the need to periodically refresh thedatabase.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
