tpcc_current (Дополнительные методические материалы), страница 24

Anau d it checklist is p rovid ed as p art of this sp ecification. Please obtain the cu rrent au d it checklist from one of theau d itors. The term "ind epend ent" is d efined as: "the ou tcom e of the benchm ark carries no financial benefit to theau d iting agency other than fees earned d irectly related to the au d it." In ad d ition, the au d iting agency cannot havesu p p lied any p erform ance consu lting u nd er contract for the benchm ark u nd er aud it. The term "certified " is d efinedas: "the TPC has review ed the qu alification of the au d itor and certified t hat the au d itor is cap able of verifyingcom p liance of the benchm ark resu lt." Please see the TPC Au d it Policy for a d etailed d escrip tion of the au d itorcertification p rocess.In ad d ition, the follow ing cond itions m u st be m et:1.The au d iting agency cannot be financially related to the sp onsor.

For exam p le, the au d iting agency isfinancially related if it is a d ep end ent d ivision, the m ajority of its stock is ow ned by the sp onsor, etc.2.The au d iting agency cannot be financially related to any one of the su p p liers of the m easu red / p ricedcom p onents, e.g., the DBMS su p p lier, the term inal or term inal concentrator su p p lier, etc.9.1.2The au d itor's attestation letter m u st be m ad e read ily available to the p u blic as p art of the FullDisclosu re Rep ort, bu t a d etailed rep ort from the au d itor is not requ ired .9.1.3For the p u rp ose of the au d it, only transactions that are generated by the Driver System and the d ataassociated w ith those transactions shou ld b e u sed for the au d it tests, w ith the excep tion of the initial d atabasep op u lation verification.9.1.4In the case of au d ited TPC-C resu lts w hich are u sed as a basis for new TPC-C resu lts, the sp onsor ofthe new benchm ark can claim that the resu lts w ere au d ited if, and only if:1.The au d itor ensu res that the hard w are and softw are prod u cts are the sam e.2.The au d itor review s the Fu ll Disclosu re Rep ort (FDR) of the new resu lts and ensu res that they m atch w hatis contained in the original sp onsor's FDR.3.The au d itor can attest to Clau ses 9.2.8.The au d itor is not requ ired to follow any of the rem aining au d itor's check list item s from Clau se 9.2.9.2Auditor's check list9.2.1 Clause 1 Logical D atabase D esign Related Items9.2.1.1Verify that sp ecified attribu tes (i.e., colu m ns) and row s exist, and that they conform to thesp ecifications.9.2.1.2Verify that th e row id entifiers are not d isk or file offsets.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 100 of 1309.2.1.3Verify that all tables su p p ort retrievals, inserts and d eletes.9.2.1.4Verify the rand om ness of the inp u t d ata to the system u nd er test for all transact ions.

Inclu d everification that the valu es generated are u niform across the entire set of row s in the configu red d atabase necessaryto su p p ort the claim ed tp m C rating p er Clau se 5.4.9.2.1.5Verify w hether any horizontal and / or vertical p artit ioning has been u sed , and , if so, w hether it w asim p lem ented in accord ance w ith the TPC-C requ irem ents.9.2.1.6Verify w hether any rep lication of tables has been u sed , and , if so, w hether it w as im p lem ented inaccord ance w ith the TPC-C requ irem ents.9.2.1.7Verify that no m ore than 1%, or no m ore than one (1), w hichever is greater, of the Deliverytransaction s skip p ed becau se there w ere few er than necessary ord ers p resent in the N ew -Ord er table.9.2.2 Clause 2 Transaction and Terminal Profiles Related Items9.2.2.1Verify that the ap p lication p rogram s m atch the resp ective transaction p rofiles.9.2.2.2Verify that the inp u t d ata satisfy the requ irem ents and that inp u t/ ou tp u t scree n layou ts are p reserved .9.2.2.3Verify com p liance w ith the error d etection and rep orting requ irem ent as sp ecified in clau se 2.3.6.Comment: This m ay be verified by cod e insp ection at the d iscretion of the au d itor.9.2.2.4Verify that each N ew -Ord er transaction u ses ind ep end ently generated inp u t d ata and not d ata fromrolled back transactions.9.2.2.5Verify that the rand om ly generated inp u t d ata satisfies the follow ing constraints:1.At least 0.9% and at m ost 1.1% of the N ew -Ord er transaction s roll back as a resu lt of an u nu sed itemnu m ber.

For these transactions the requ ired p rofile is execu ted , and the correct screen is d isp layed .Furtherm ore, verify that the ap p lication m akes only p erm itted u se of the fact that the inp u t d ata containsan u nu sed item nu m ber.2.The average nu m ber of ord er-lines p er ord er is in the range of 9.5 to 10.5 and the nu m ber of ord er -lines isu niform ly d istribu ted from 5 to 15 for the N ew -Ord er transaction s that are su bm itted to the SUT d u ringthe m easu rem ent interval.3.The nu m ber of rem ote ord er-lines is at least 0.95% and at m ost 1.05% of the nu m ber of ord er -lines that arefilled in by the N ew -Ord er transaction s that are su bm itted to the SUT d u ring the m easu rem ent interval,and the rem ote w arehou se nu m bers are u niform ly d istribu ted w ithin the range of active w arehou ses (seeClau se 4.2.2).4.The nu m ber of rem ote Paym ent transaction s is at least 14% and at m ost 16% of the nu m ber of Paym enttransactions that are su bm itted to the SUT d u ring the m easu rem ent interval, and the rem ote w arehou senu m bers are u niform ly d istribu ted w ithin the range of active w arehou ses (see Clau se 4.2.2).5.The nu m ber of cu stom er selections by cu stom er last nam e in the Paym ent transaction is at least 57% and atm ost 63% of the nu m ber of Paym ent transactions that are su bm itted to the SUT d u ring the m easu rem entinterval.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 101 of 1306.The nu m ber of cu stom er selections by cu stom er last nam e in the Ord er-Statu s transaction is at least 57%and at m ost 63% of the n u m ber of Ord er -Statu s transactions that are su bm itted to the SUT d u ring them easu rem ent interval.9.2.2.6Verify that resu lts from execu ting the Delivery transaction in d eferred m od e are record ed into a resu ltfile.

Verify that the resu lt file is m aintained on the p rop er typ e of d u rable m ed iu m . Furtherm ore, verify that noaction is record ed into the resu lt file u ntil after the action has been com p leted .9.2.2.7transaction.Verify that all inp u t and ou tp u t field s that m ay change on screens are clear ed at the beginning of each9.2.2.8Using one of the configu red term inals, verify that the inp u t/ ou tp u t screen for each transaction typ esp rovid es all the featu res d escribed in Clau se 2.2.2.4.9.2.2.9The au d itor can fu rther verify the com p liance of the inp u t d ata by qu erying the follow ing attribu tes:• O_ALL_LOCAL can be u sed to verify that ap p roxim ately 10% of all ord ers contain at least one rem ote ord er line.• C_PAYMEN T_CN T can be u sed to verify that w ithin the Paym ent tran saction cu stom ers w ere selectedaccord ing to the requ ired non -u niform rand om d istribu tion.• S_YTD can be u sed to verify that w ithin the N ew -Ord er transaction the qu antity ord ered for each item w asw ithin the requ ired range.• S_ORDER_CN T can be u sed to verify that w ithin the N ew -Ord er transaction item s w ere selected accord ing tothe requ ired non-u niform rand om d istribu tion.• S_REMOTE_CN T can be u sed to verify that w ithin the N ew -Ord er transaction rem ote ord er-lines w ereselected accord ing to the requ ired u niform rand om d istribu tion.9.2.39.2.3.19.2.49.2.4.1Clause 3 Transactions and System Properties Related ItemsVerify that the requ irem ents of each of the ACID tests w ere m et.Clause 4 Scaling and D atabase Population Related ItemsVerify that the d atabase is initially p op u lated w ith the p rop erly scaled requ ired p op u lation.9.2.4.2Verify the correct card inalities of the nine d atabase tables, at the start of the benchm ark ru n as w ell asat the end of it, and that the grow th in the N ew -Ord er table, in p articu lar, is consistent w ith the nu m ber and typ e ofexecu ted transactions.9.2.6Clause 5 Performance Metrics and Response Time Related Items9.2.6.1m ix.Verify that the m ix of transactions as seen by the SUT satisfies the requ ired m inim u m p ercentage of9.2.6.2Verify the valid ity of the m ethod u sed to m easu re the resp onse tim e at the RTE.9.2.6.3If p art of the SUT is em u lated , verify that the rep orted resp onse tim e is no less than the resp onse tim ethat w ou ld be seen by a real term inal u ser.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 102 of 1309.2.6.4Verify the m ethod u sed to d eterm ine that the SUT had reached a stead y state p rior to com m encing them easu rem ent interval (see Clau se 5.5).9.2.6.5Verify that all w ork norm ally d one in a stead y state environm ent actu ally occu rred d u ring them easu rem ent interval, for exam p le checkp ointing, w riting red o/ u nd o log record s to d isk, etc.9.2.6.6Verify the d u ration of the m easu rem ent interval for the rep orted tp m C.9.2.6.7Verify that the resp onse tim es have been m easu red in the sam e tim e interval as the test.9.2.6.8Verify that th e requ ired Keying and Think Tim es for the em u lated u sers occu r in accord ance w ith th erequ irem ents.9.2.6.9Verify that the 90th p ercentile resp onse tim e for each transaction typ e is greater than or equ al to theaverage resp onse tim e of that transaction typ e.9.2.6.10If the RTE ad ju sts the w eights associated to each transaction typ e, verify that these ad ju stm ents havebeen lim ited to keep the w eights w ithin 5% on either sid e of their resp ective initial valu e.9.2.6.11If the RTE u ses card d ecks (see Clau se 5.2.4.2) verify that they m eet the requ irem ents.9.2.6.12If p eriod ic checkp oints are u sed , verify that they are p rop erly sched u led and execu t ed d u ring them easu rem ent interval.9.2.6.13Verify that the average think tim e for each transaction typ e is equ al to or greater than the m inim umsp ecified in Clau se 5.2.5.79.2.7Clause 6 SUT, D river, and Communications D efinition Related Items9.2.7.1Describe the m ethod u sed to verify the accu rate em u lation of the tested term inal p op u lation by theDriver System if one w as u sed .9.2.7.2Verify term inal connectivity an d context m aintenance as requ ired in Clau se 6.6.2.9.2.7.3Verify that the restrictions on op erator intervention are m et.9.2.8Clause 7 Pricing Related Items9.2.8.1Ru les for verification of p ricing related item s are inclu d ed in the cu rr ent revision of the TPC PricingSp ecification, located at w w w .tp c.org.9.2.9TPC-Energy Related Items9.2.9.1When the op tional TPC-Energy stand ard is u sed , the ad d itional au d it requ irem ents m u st be follo w ed .In ad d ition, the requ irem ents of the TPC-Energy Sp ecification, located at w w w .tp c.org, m u st be m et.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 103 of 1309.2.10Full D isclosure Related Items9.2.10.1Verify that the enabled num bers of p rocessors, cor es and thread s rep orted by the test sp onsor areconsistent w ith those rep orted by the op erating system and that any p rocessors, cores or thread s that existed on theSUT, bu t are claim ed as d isabled , d o not contribu te to the p erform ance of the benchm ark.9.2.10.2Any DBMS artifact, u tilized in a TPC-C ap p lication, requ ires p u blic d ocu m entation or a letter from theDBMS vend or to the au d itor, d escribing the behavior and ongoing su p p ort of the sam e behavior.Comment: For exam p le, a DBMS artifact is the selection of row s in the ord er of the p rim ary ind ex even thou gh thereis no ORDER BY clau se in the cu rsor d efinition.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 104 of 130Index55-year pricing 83, 85990th percentile response tim e 70, 74, 79, 99AACID 6, 20, 37, 40, 44, 46, 54, 72, 78, 84, 90, 98Ad d ing 18Application 6, 7, 9, 17, 18, 19, 20, 21, 23, 25, 26, 27, 30, 47, 51,82, 83, 85, 86, 87, 97Arbitrary 19, 50, 51Atom icity 46Attributes 17Aud itor's check list 96Data m anipulation 19, 25, 29, 90Database transaction 20, 23, 25, 27, 28, 29, 33, 34, 36, 37, 39,40, 41, 42, 43, 44, 46, 47, 50, 53Deck 69, 94, 99Deletes 18, 50, 96Deleting 18Delivery transaction 39, 41, 50, 53, 54, 67, 68, 70, 71, 73, 80,90, 94, 97, 98, 109Dirty read 50Dirty w rite 50District 12, 28, 33, 43, 46, 47, 48, 58, 60, 64, 65Driver 58, 78, 79, 80, 81, 83, 94, 96, 99Durability 46, 56, 57Durable 56Dynam ic-space 61EEm ulated users 67Executive sum m ary 125FBBound aries 17Business transaction 20, 24, 25, 27, 32, 36, 39, 40, 41, 43, 44,53, 67, 68, 71Free-space 61Front-end system s 78, 95Full Disclosure Report ∑7, 22, 46, 80, 81, 82, 86, 95, 96, 127HCC_LAST 13, 20, 28, 30, 31, 32, 33, 34, 35, 36, 37, 38, 62, 65, 89,90, 92Card inality 10, 18, 59, 60, 66, 90Checkpoint 58, 73, 86, 93, 94, 99, 127Checkpoint interval 73, 94Com m ercially available 6, 19, 21, 25, 26, 79, 82, 84, 90Com m it 47, 50, 51, 52, 53, 54, 55, 104, 106, 108, 109, 111, 114,115, 116, 118, 119, 120, 122Com m itted 18, 24, 29, 31, 34, 37, 40, 42, 44, 50, 56, 57, 58, 67,84Concentration 81Consistency 46, 47, 48, 49, 58, 87Context 9, 14, 26, 47, 54, 80, 81Custom er 13, 25, 28, 33, 36, 37, 42, 46, 47, 49, 60, 65, 89, 92H ard w are 7, 17, 19, 25, 58, 78, 79, 81, 82, 94, 96H ashing 18H orizontal partitioning 17IInserts 18, 88, 96, 119Integrity 18Isolation 46, 50, 51, 52, 53, 54, 55, 90KKeying tim e 68, 69, 70DLDaily-grow th 61Daily-spread 61LAN 11, 13, 33, 35, 36, 37, 38, 42, 49, 53, 65, 87, 88, 89, 92Last nam e 20, 22, 28, 32, 33, 35, 36, 37, 38, 62, 73, 94, 97, 123TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 105 of 130Load balancing 25Locking 6, 51, 87Logical database d esign 88, 96MMeasurem ent interval 10, 27, 32, 36, 39, 40, 46, 49, 58, 61, 67,68, 69, 71, 72, 73, 74, 75, 84, 86, 93, 94, 97, 98, 99, 127Mem ory 40, 56, 57, 84, 87, 88, 95Menu 22, 67, 68Mirroring 56, 57Mix I, 3, 6, 7, 47, 68, 69, 70, 71, 72, 74, 78, 84, 86, 88, 90, 94, 98Mod ifying 18Multiplexing 25, 79, 80RRand om 20, 27, 32, 36, 39, 43, 46, 47, 49, 53, 54, 60, 62, 63, 64,65, 66, 68, 69, 84, 90, 94, 97, 98, 123Rand om ly 20, 27, 32, 36, 39, 46, 47, 49, 54, 65, 69, 84, 97Recovery 25, 84, 87Rem ote ord er-lines 72, 90, 94, 97, 98Rem ote p aym ent transaction 72, 90, 94, 97Replicated table 17, 54Replication 17, 89Response tim e 67Response tim e constraints 69Rollback 47, 50, 104, 123Roll-forw ard 58, 84Routers 87, 88, 95RTE 20, 23, 57, 69, 70, 71, 72, 77, 78, 79, 80, 81, 94, 98, 99NN etw ork configuration 81N ew -Ord er 14, 28, 41, 47, 48, 49, 54, 55, 59, 60, 66, 84, 90N ew -Ord er transaction 25, 27, 29, 31, 50, 51, 52, 53, 54, 55,58, 66, 67, 68, 69, 70, 71, 72, 74, 75, 90, 93, 94, 97, 98, 103N inetieth percentile 93N on-repeatable read 50N on-uniform 20, 27, 32, 36, 65, 98, 123N on-volatile 56N URand 20, 27, 32, 36, 65, 112, 120SScaling 59, 90, 98Space 10, 18, 22, 23, 30, 34, 37, 40, 44, 59, 60, 61, 66, 72, 84, 93Static-space 61Stock-Level transaction 43, 45, 46, 50, 51, 67, 68, 111Storage 18, 56, 59, 60, 61, 66, 78, 83, 84, 90SUT 20, 23, 25, 27, 28, 32, 33, 36, 39, 40, 43, 46, 49, 58, 59, 67,68, 70, 71, 72, 73, 77, 78, 79, 80, 81, 82, 83, 85, 88, 90, 93, 94,95, 97, 98, 99OTOperating system 17, 19, 42, 46, 57, 65, 66Ord er 14, 15, 16, 28, 29, 37, 41, 42, 43, 47, 48, 49, 54, 55, 58, 59,60, 61, 64, 66, 84, 90, 92, 98, 103, 105, 107, 109Ord er-Line 29, 48, 49, 59, 60, 61, 84Ord er-Status transaction 36, 38, 50, 51, 52, 55, 68, 73, 90, 94,97, 107Over-scaling 60Term inal 6, 20, 21, 22, 23, 25, 27, 29, 30, 31, 32, 34, 35, 36, 37,38, 39, 40, 41, 43, 44, 45, 57, 58, 59, 60, 68, 69, 70, 71, 74, 78,79, 80, 81, 83, 84, 86, 87, 90, 95, 96, 98, 99, 103Test sponsor 22, 25, 41, 46, 51, 54, 58, 67, 68, 72, 80, 81, 95Think tim e 68, 70, 74, 75, 93, 99, 127Throughput 6, 54, 59, 60, 61, 67, 68, 70, 71, 72, 73, 74, 75, 79,82, 85, 93Tim estam p 25, 70, 71, 103, 105, 109, 112, 113, 120, 121, 122TPC Aud itor 58TPC-C transactions 46, 47, 51, 58, 92, 103tpm C 3, 6, 49, 58, 59, 61, 71, 72, 75, 78, 81, 83, 84, 85, 86, 93,94, 97, 99, 127Transaction m ix 7, 68, 69, 70, 71, 72, 74, 78, 84, 86, 88, 94, 127Transaction m onitors 25, 26, 87Transaction profiles 17, 21, 25, 56, 59, 97Transaction RT 25, 68, 69, 71Transparency 18, 26PPacing 67Partitioned d ata 18, 19, 89Paym ent transaction 32, 33, 35, 46, 47, 50, 53, 68, 72, 73, 90,94, 97, 98, 105Perform ance m etrics 67, 93, 98Phantom 50Pow er supply 78Precision 11, 18, 20, 62, 85Priced configuration 83Pricing 83, 84, 99Prim ary key 14, 18, 32, 36, 90UUninterruptible Pow er Supply 56, 57, 85Unique 10, 11, 12, 13, 14, 15, 16, 18, 20, 29, 32, 36, 43, 62, 63,64, 65, 66, 87TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 106 of 130VWVertical partitioning 17Warehouse 11, 28, 33, 46, 47, 48, 59, 60, 63, 64, 90Workstations 78, 80, 87, 88TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 107 of 130Appendix A: SAMPLE PROGRAMSThe follow ing are exam p les of the TPC-C transactions and d atabase load p rogram in SQL em bed d ed in C.