Re: The term "Transactions Per Second"
Date: 27 Mar 1994 20:38:21 -0500
Message-ID: <2n5ced$i2o_at_infochi.com>
Ramzi BAROODY (rbaroody_at_cs.mcgill.ca) wrote:
: If someone says that a certain server can perform 282 TPS (transactions
: Ramzi
: per seconds) under Oracle 7, then what exactly does this measure indicate?
: What is considered as a transaction in this case?
Hi Ramzi.
A transaction is a logical unit of work which is all the database updates that are performed between the beginning of a transaction and the COMMIT. Some transactions can be long and others short. For the sake of illustration let's say that a really fast operator can complete a transaction in 60 seconds. This means that 60 operators would be able to processs one TPS. In order to create 280 transcation in a second, there would have to be about 17,000 concurrent users!
What you are probably being told refers to some cooked up becnhmark which Oracle and other RDBMS vendors run called the TPC-A benchmark. It is a benchmark designed by RDBMS vendors to make their products look far more capable than they really are. The new TPC-C benchmark gives more realistic results but the TPC committee of RDBMS vendors changed the metric so that it now reads as TPM (transactions per minute). These guys are really something else.
If you want to read more about TPC benchmarks, David McGoveran has an excellent discussion of it in the February issue of Network Computing. Basically he finds it a highly politicized and misleading benchmark. I agree. BTW, one consultant who wrote a stinging report concerning the Oracle "discrete transaction" which Oracle used to get their exaggerated results is currently being sued by Oracle.
- Rich
-- Richard Finkelstein Voice: 312-549-8325 Performance Computing, Inc. Fax: 312-549-4824 Chicago, IL Mail: rfinkel_at_infochi.comReceived on Mon Mar 28 1994 - 03:38:21 CEST