tpcc_current (1034761), страница 19
Текст из файла (страница 19)
At som e su bsequ ent tim e, the m od ified record s/ p ages are w ritten tom ake the d u rable cop y cu rrent. This p rocess is d efined as a checkp oint in this d ocu m ent.For system s w hich d efer d atabase w rite to d u rable m ed ia, it is a requ irem ent that:1.The tim e betw een check points (know n as the Checkp oint Interval (CI)), m u st be less than or equ al to 30m inu tes. The Checkp oint Du ration , tim e requ ired by the DBMS to w rite m od ified d atabase record s/ p agesto d u rable m ed ia, m u st be less than or equ al to the Checkp oint Interval.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 75 of 130Comment: For system s w hich recover from instantaneou s interru p tions by ap p lying recovery d ata to thed atabase stored on d u rable m ed ia (d atabase system s that d o not p erform checkp oints), it is a requ irem entthat no recovery d ata old er than 30 m inu tes p rior to the interru p tion be u sed .
The consequ ence of thisrequ irem ent is that the d atabase contents stored on d u rable m ed ia cannot at any tim e d u ring theMeasu rem ent Interval (MI) be m ore than 30 m inu tes old er than the m ost cu rrent state of the d atabase(±5%).2.5.6All w ork requ ired to p erform a checkp oint m u st occu r at least once before, d u ring stead y state, and at leastfou r tim es d u ring the Measu rem ent Interval. The start tim e and d u ration in second s of at least the fou rlongest checkp oints d u ring the Measu rem ent Interval m u st be d isclosed ..Required Reporting5.6.1The frequ ency d istribu tion of resp onse tim es of all transactions, started and com p leted d u ring them easu rem ent interval, m ust be rep orted ind ep end ently for each of the five transaction typ es (i.e., N ew -Ord er,Paym ent, Ord er-Statu s, Delivery, and Stock-Level).
The x-axis rep resents the transaction RT and m u st range from 0to fou r tim es the m easu red 90th p ercentile RT (N ) for that transaction. The y -axis rep resents the frequ ency of thetransactions at a given RT. At least 20 d ifferent intervals, of equ al length, m u st be rep orted . The m axim u m , average,and 90th p ercentile resp onse tim es m u st also be rep orted . An exam p le of su ch a grap h is show n below .A verage Res pon se T ime90 th P erce ntil eResp ons e Ti meNumbe r ofT ra nsa ctio ns0NResp ons e Ti me (sec .)4NTPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 76 of 1305.6.2A grap h of resp onse tim es versu s throu ghp u t for the N ew -Ord er transaction , ru n w ithin the m ixrequ ired in Clau se 5.2.3, m u st be rep orted .
The x-axis rep resents the m easu red N ew -Ord er throu ghp u t. The y-axisrep resents the corresp ond ing 90th p ercentile of resp onse tim es. A grap h m u st be p lotted at ap p roxim ately 50%, 80%,and 100% of rep orted throu ghp u t rate (ad d itional d ata p oints are op tional). The 50% and 80% d ata p oints are to bem easu red on the sam e configu ration as the 100% ru n, for a m inim u m interval of 20 m inu tes, varying either theThink Tim e of one or m ore transaction typ es or the nu m ber of active term inals. Interp olation of the grap h betw eenthese d ata p oints is p erm itted . Deviations from the requ ired transaction m ix are perm itted for the 50% and 80% d atap oints. An exam p le of su ch a grap h is show n below .90 th P erce ntil eResp ons e Ti me5s ec.Repo rted MQTh050 %80 %10 0%MQT h5.6.3The frequ ency d istribu tion of Think Tim es for the N ew -Ord er transaction , started and com p letedd u ring the m easu rem ent interval, m u st be rep orted .
The x-axis rep resents the Think Tim e and m u st range from 0 tofou r tim es the actu al m ean of Think Tim e for that transaction. The y -axis rep resents the frequ ency of the transaction sw ith a given Think Tim e. At least 20 d ifferent intervals, of equ al length, m u st be rep orted . The m ean Think Tim em u st also be rep orted .
An exam p le of su ch a grap h is show n below .Th in k Time Fre que ncyMean T hi nk T ime012 .5T hi nk Ti me (sec .)50TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 77 of 1305.6.4A grap h of the throu ghp u t of the N ew -Ord er transaction versu s elap sed tim e (i.e., w all clock) m u st berep orted for both ram p -u p tim e and m easu rem ent interval. The x-axis rep resents the elap sed tim e from the start ofthe ru n. The y-axis rep resents the throu ghp u t in tp m C. At least 240 d ifferent intervals shou ld be u sed w ith am axim u m interval size of 30 second s. The op ening and the closing of the m easu rem ent interval m u st also berep orted and show n on the grap h.
The start tim e for each of the checkp oints m u st be ind icated on the grap h. Anexam p le of su ch a grap h is show n below .MQThRamp-upSteady StateMeasurement IntervalStart0Ramp-downMeasurement IntervalEndElapsed Time (sec.)5.7 Primary MetricsTo be com p liant w ith the TPC-C stand ard and the TPC‟ s Fair Use Policies and Gu id elines, all p u blicreferences to TPC-C resu lts for a configu ration m u st inclu d e the follow ing com p onents w hich w ill beknow n as the Prim ary Metrics.5.7.1The TPC-C Maxim um Qu alified Throu ghp u t (MQTh) rating exp ressed in tp m C. This is know n as thePerform ance Metric. (See Clau se 5.4.)The TPC-C total 3-year p ricing d ivid ed by the MQTh and exp ressed as p rice/ tp m C.
This is also know nas the Price/ Perform ance m etric. (See Clau se 7.3.)The d ate w hen all p rod u cts necessary to achieve the stated p erform ance w ill be available (stated as asingle d ate on the execu tive su m m ary). This is know n as the availability d ate. (See Clau se 8.1.8.3.)When the op tional TPC-Energy stand ard is u sed , the ad d itional p rim ar y m etric exp ressed asw atts/ Ktp m C m u st be rep orted . In ad d ition, the requ irem ents of the TPC -Energy Sp ecification, locatedat w w w .tp c.org, m u st be m et.TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 78 of 130Clause 6: SUT, D RIVER, and COMMUN ICATION S D EFIN ITION6.1Models of the Target SystemSom e exam p les of a system w hich rep resents the target (object) of this benchm ark are show n p ictorially below .
Byw ay of illu stration, the figu res also d ep ict the RTE/ SUT bou nd ary (see Clau ses 6.3 and 6.4) w here the resp onse tim eis m easu red .Example 1RTETerminal NetworkSUTServ er Sy stem(s)TSERVERTNetwork*S-SNetwork*SUTLegend: C = ClientK/D = Key board/DisplayRTE = Remote Terminal EmulatorS= Serv erSUT = Sy stem Under TestT= TerminalWS = Workstation*= OptionalTExample 2RTESUTServ er Sy stem(s)Response Time Measured HereK/DwsWS - SNetwork*ws*K/DExample 3RTETerminal NetworkSUTServ er Sy stem(s)Client Sy stem(s)TTC-SNetwork*SERVERS-SNetwork**TNetwork*CLIENTTPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 79 of 130SERVERS-SNetwork*6.2Test ConfigurationThe test configu ration consists of the follow ing elem ents:• System Und er Test (SUT)• Driver System (s)• Driver/ SUT Com m u nications Interface(s)If one of the netw orks is a WAN , the tested configu rations need not inclu d e th e WAN long -hau l com m u nicationslines.6.3System Under Test (SUT) D efinition6.3.1The SUT consists of:• One or m ore p rocessing u nits (e.g., host, front -end s, w orkstations, etc.) w hich w ill ru n the transaction m ixd escribed in Clau se 5.2.3, and w hose aggregate p erform ance (total Maxim u m Qu alified Throu ghp u t) w ill bed escribed by the m etric tp m C.• Any front-end system s are consid ered to be p art of the SUT.
Exam p les of front-end system s are front-endd ata com m unication p rocessors, clu ster controllers, d atabase clients (as in the client/ server m od el), andw orkstations.• The host system (s), inclu d ing hard w are and softw are, su p p orting the d atabase em p loyed in the benchm ark.• The hard w are and softw are com p onents of all netw orks requ ired to con nect and su p p ort the SUTcom p onents.• Data storage m ed ia su fficient to satisfy both the scalin g requ irem ents in Clau se 4.2 and the ACID p rop ertiesof Clau se 3.6.3.2A single benchm ark resu lt m ay be u sed for m u ltip le SUTs p rovid ed the follow in g cond itions are m et:• Each SUT m u st have the sam e hard w are and softw are architectu re and configu ration.• The only excep tion allow ed are for elem ents not involved in the p rocessing logic of the SUT (e.g., num ber ofp erip heral slots, p ow er su p p ly, cabinetry, fans, etc.)• Each SUT m u st su p p ort the p riced configu ration.6.4D river D efinition6.4.1An external Driver System (s), w hich p rovid es Rem ote Term inal Em u lator (RTE) fu nctionality, m u st beu sed to em u late the target term inal p op u lation and their em u lated u sers d u ring the benchm ark ru n.6.4.2The RTE p erform s the follow ing fu nctions:• Em u lates a u ser entering inp u t d ata on the inp u t/ ou tp u t screen of an em u lated term inal by generating andsend ing transactional m essages to the SUT;• Em u lates a term inal d isp laying ou tp u t m essages on an inp u t/ ou tp u t scr een by receiving resp onse m essagesfrom the SUT;TPC Benchm ark™C - Stand ard Sp ecification, Revision 5.11 - Page 80 of 130• Record s resp onse tim es;• Perform s conversion and / or m u ltip lexing into the com m u nications p rotocol u sed by the com m u nicationsinterface betw een the d river and the SUT ;• Perform s statistical accou nting (e.g., 90th p ercentile resp onse tim e m easu rem ent, throu ghp u t calcu lation, etc.)is also consid ered an RTE fu nction.6.4.3N orm ally, the Driver System is exp ected to p erform RTE fu nctions only.
Work d one on the DriverSystem in ad d ition to the RTE as sp ecified in Clau se 6.4.2 m u st be thorou ghly ju stified as sp ecified in Clau se 6.6.3.6.4.4The intent is that the Driver System m u st reflect the p rop osed term inal configu ration and cannot ad dfu nctionality or p erform ance above the p riced netw ork com p onents in the SUT. It m u st be d em onstrated thatp erform ance resu lts are not enhanced by u sing a Driver System .6.4.5Softw are or hard w are w hich resid es on the Driver w hich is not the RTE is to be consid ered as p art ofthe SUT. For exam p le, in a "client/ server" m od el, the client softw are m ay be ru n or be sim u lated on the DriverSystem (see Clau se 6.6.3).6.5Communications Interface D efinitions6.5.1I/O Channel Connections6.5.1.1All p rotocols u sed m u st be com m ercially available.Comment: It is the intention of this d efinition to exclu d e non -stand ard I/ O channel connections.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
