Author: Robert Hyatt
Date: 18:25:04 02/23/03
Go up one level in this thread
On February 23, 2003 at 01:50:31, Jeremiah Penery wrote: >On February 23, 2003 at 00:53:51, Robert Hyatt wrote: > >>On February 22, 2003 at 20:06:44, Jeremiah Penery wrote: >> >>>If you don't like SPEC, look at TPC numbers. >> >>Let's back up to reality a minute. Servers have one type of requirement. >>workstations have another. I'm not about to talk about the PC platform as >>a high-performance server. It is _not_. The raw PCI bus is completely >>unable to sustain the kind of bandwidth that the high-end server market is >>all about, and that is a problem. Doesn't matter how fast the CPU goes. >> >>Just compare the I/O bandwidth of "server machines" with the I/O bandwidth >>of a PC and you will see what I mean. > >Do you have any clue what TPC benchmarks are all about? No, I thought not. TPC >are SERVER benchmarks, heavily stressing on I/O performance! And look at the machines you quote. Who cares about a machine that is a big cluster of slow machines that can handle a large TPC? Just because such cluster architectures dominate some particular niche, doesn't mean they work for all large server applications. Dunn and Bradstreet in NY comes to mind. But so do others. Any time you want to compare I/O throughput on any PC of your choice against an alpha server here, I'll provide some benchmark data. But we are talking about a database that is _not_ split into tiny parts on a pile of PCs. One database, on one machine, spread over say 64 drives... The PC simply doesn't address that market. The NUMA Itaniums are up there of course but they aren't PCs. > >I'll go ahead and quote most of the page here, just so you don't have to follow >the link: http://www.tpc.org/information/benchmarks.asp > >------------------ > >TPC-C >TPC-C simulates a complete computing environment where a population of users >executes transactions against a database. The benchmark is centered around the >principal activities (transactions) of an order-entry environment. These >transactions include entering and delivering orders, recording payments, >checking the status of orders, and monitoring the level of stock at the >warehouses. While the benchmark portrays the activity of a wholesale supplier, >TPC-C is not limited to the activity of any particular business segment, but, >rather represents any industry that must manage, sell, or distribute a product >or service. > >TPC-C involves a mix of five concurrent transactions of different types and >complexity either executed on-line or queued for deferred execution. It does so >by exercising a breadth of system components associated with such environments, >which are characterized by: > >The simultaneous execution of multiple transaction types that span a breadth of >complexity >On-line and deferred transaction execution modes >Multiple on-line terminal sessions >Moderate system and application execution time >Significant disk input/output >Transaction integrity (ACID properties) >Non-uniform distribution of data access through primary and secondary keys >Databases consisting of many tables with a wide variety of sizes, attributes, >and relationships >Contention on data access and update >TPC-C performance is measured in new-order transactions per minute. > > >TPC-H >The TPC Benchmarkâ˘H (TPC-H) is a decision support benchmark. It consists of a >suite of business oriented ad-hoc queries and concurrent data modifications. The >queries and the data populating the database have been chosen to have broad >industry-wide relevance. This benchmark illustrates decision support systems >that examine large volumes of data, execute queries with a high degree of >complexity, and give answers to critical business questions. > >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 include the >selected database size against which the queries are executed, the query >processing power when queries are submitted by a single stream, and the query >throughput when queries are submitted by multiple concurrent users. > > >TPC-W >TPC Benchmark⢠W (TPC-W) is a transactional web benchmark. The workload is >performed in a controlled internet commerce environment that simulates the >activities of a business oriented transactional web server. The workload >exercises a breadth of system components associated with such environments, >which are characterized by: >Multiple on-line browser sessions >Dynamic page generation with database access and update >Consistent web objects >The simultaneous execution of multiple transaction types that span a breadth of >complexity >On-line transaction execution modes >Databases consisting of many tables with a wide variety of sizes, attributes, >and relationships >Transaction integrity (ACID properties) >Contention on data access and update >The performance metric reported by TPC-W is the number of web interactions >processed per second. Multiple web interactions are used to simulate the >activity of a retail store, and each interaction is subject to a response time >constraint. > >TPC-W simulates three different profiles by varying the ratio of browse to buy: >primarily shopping (WIPS), browsing (WIPSb) and web-based ordering (WIPSo).
This page took 0.01 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.