Tools and Techniques for Preliminary Sizing of Transaction Processing Applications. Digital VAX 6000, VAX TPC Benchmark A, VAX DECtp, VAX DECdta, VAX ACMS, VAX Server, VAX ft, VAX 9000, VAX cluster, VAX KODA
विज्ञापन
विज्ञापन
William Z Zahuvi
Frances A. Habib
KennethJ. Omahen
I
Tools and Techniques for Preliminary
Sizing of Transaction Processing
Applications
Sizing transaction processing systems correctly is
a
difficzilt tmk. BJ~ action processing applicatious are notpredefined and can
u n q ~
the complex. Siring during the analysis and design stages of the cipplication devel- opment cycle is particularly difficult. It is impossible to measure the resource requirements of an application uhich is not yet written or fully implemented. To make sizing easier and more accurate in these stages, a sizing methodologby was developed that uses measurements from systems on zvhich industry-standard benchmarks have been run and employs standard systems analysis techniques for acquiring sizing information. These metrics are then used to predict future trans- action resource usage.
The transaction processing marketplace is domi- nated by commercial applications that support businesses. These applications contribute substan- tially to the success or failure of a business, based on the level of performance the application provides.
In transaction processing, poor application perfor- mance can translate directly into lost revenues.
The risk of implementing a transaction process- ing application that performs poorly can be mini- mized by estimating the proper system size in the early stages of application development. Sizing esti- mation includes configuring the correct processor and proper number of disk drives and controllers, given the characteristics of the application.
The sizing of transaction processing systems is a difficult activity. Unlike traditional applications such as mail, transaction processing applications are not predefined. Each customer's requirement is different and can vary from simple to complex.
'Therefore, Digital chose to develop a sizing method- ology that specifically meets the unique require- ments of transaction processing customers. The goal of this effort was to develop sizing tools and techniques that would help marketing groups and design consultants in recommending configura- tions that meet the needs of Digital's customers.
Digital's methodology evolved over time, as experi- ence was gained in dealing with the real-world problems of transaction processing system sizing.
The development of Digital's transaction process ing sizing methodology was guided by several prin- ciples. The first principle is that the methodology should rely heavily upon measurements of Digital systems running industry-standard transaction processing benchmarks. These benchmarks pro- vide valuable data that cluantifies the performance characteristics of different hardware and software configurations.
The second principle is that systems analysis methodologies should be used to provide a frame- work for acquiring sizing information. In partic- ular, a multilevel view of a customer's business is adopted. This approach recognizes that a man- ager's view of the business functions performed by an organization is different from a computer ana- lyst's view of the transaction processing activity.
The sizing methodology should accommodate both these views.
The third principle is that the sizing methodol- ogy must employ tools and techniques appropriate to the current stage of the customer's application design cycle. Early in the effort to develop a sizing methodology, it was found that a distinction must be made between preliminary sizing and sizing during later stages of the application development cycle. Preliminary sizing occurs during the analysis and design stages of the application development cycle. Therefore, no application software exists
Vol.
.3
i\'o.
I
Wirrler
1991
Digital Technical
Journal
Tools and Techniques for Preliminary Sizing of Transaction Processing Applications
which can be measured. Application software does exist in later stages of the application development cycle, and its measurement provides valuable input for more precise sizing activities.
For example, if a customer is in the analysis or design stages of the application development cycle, it is unlikely that estimates can be obtained for such quantities as paging rates or memory usage.
However, if the application is fully implemented, then tools such as the VAXcluster Performance
Advisor
(VPA) and the DECcp capacity planning products can be used for sizing. These tools pro- vide facilities for measuring and analyzing data from a running system and for using the data as input to queuing models.
The term sizing, as used in this paper, refers to preliminary sizing. The paper presents the metrics and algebra used in the sizing process for DECtp applications. It also describes the individual tools developed as part of Digital's transaction process- ing sizing effort.
Sizing
The purpose of sizing tools is twofold. First, sizing tools are used to select the appropriate system components and to estimate the performance level of the system in terms of device utilization and user response times. Second, sizing tools bridge the gap between business specialists and computer specialists. This bridge translates the business units into functions that are performed on the system and, ultimately, into units of work that can be quan- tified and measured in terms of system resources.
In the sections that follow, a number of important elements of the sizing methodology are described.
The first of these elements is the platform on which the transaction processing system will be imple- mented. It is assumed that the customer will supply general preferences for the software and hardware configuration as part of the platform information.
The Levels of Business Metrics section details the multilevel approach used to describe the work per- formed by the business. The Sizing Metrics and
Sizing Formulas sections describe the algorithms that use platform and business metric information to perform transaction processing system sizing.
Platforms
The term platform is used in transaction process- ing sizing methodology to encompass general cus- tomer preferences for the hardware and software upon which the transaction processing application will run.
The hardware platform specifies the desired topology or processing style. For example, process ing style includes a centralized configuration and a front-end and back-end configuration as valid alter- natives. The hardware platform may also include specific hardware components within the process- ing style. (In this paper, the term processor refers to the overall processing unit, which may be com- posed of multiple CPUs.)
The software platform identifies the set of layered products to be used by the transaction processing application, with each software product identified by its name and version number. In the transaction processing environment, a software platform is composed of the transaction processing monitor, forms manager, database management system, appli- cation language, and operating system.
Different combinations of software platforms may be configured, depending on the hardware plat- form used.
A
centralized configuration contains all the software components on the same system. A distributed system is comprised of a front-end pro- cessor and a back-end processor; different software platforms may exist on each processor.
Levels of Business
Metrics
The term business metrics refers collectively to the various ways to measure the work associated with a customer's business. In this section, various levels of business metrics are identified and the relationship between metrics at different levels is described! As mentioned earlier, the levels corre- spond to the multilevel view of business operation typically used for systems analysis. The organi- zation or personnel most interested in a metric in relation to its business operation is noted in the discussion of each metric.
The decomposition of the business application requirements into components that can be counted and quantified in terms of resource usage requires that a set of metrics be defined. These metrics reflect the business activity and the system load.
The business metrics are the foundation for the development of several transaction processing siz- ing tools and for a consistent algebra that connects the business units with the computer units.
The business metrics are natural forecasting units, business functions, transactions, and the number of I/Os per transaction. The relationship among these levels is shown in Figure 1. In general, a busi- ness may have one or more natural forecasting units. Each natural forecasting unit may drive one or more business functions.
A
business function may
Digital
Technical Journal V o 1 . 3 No.
1
Winter
1991
Transaction Processing, Databases,
and
Fault-tolerant Systems
I
NATURAL
FORECASTING
I
NATURAL
FORECASTING
BUSINESS
FUNCTION FUNCTION FUNCTION
I I I I I
I
I
I
TRANSACTIONS
TRANSACTIONS
TRANSACTIONS TRANSACTIONS
TRANSACTIONS TRANSACTIONS
FILES
T -
READS
I10 ACTIVITY REQUIREMENTS
INSERTS
UPDATE
READS
UPDATE
WRITES
I
Figure I Levels of Business Activity Characterization
have multiple transactions, and a single transaction may be activated by different business functions.
Every transaction issues a variety of
1/0 operations to one or more files, which may be pl~ysically located on zero, one, or more disks. This section discusses the business metrics but does not dis- cuss the physical distribution of I/Os across disks, which is an implementation-specific item.
A
natural forecasting unit is a macrolevel indica- tor of business volume. (It is also called a key vol- ume indicator.)
A
business generally uses a volume indicator to measure the level of success of the business. The volume is often measured in time intervals that reflect the business cycle, such as weekly, monthly, or quarterly. For example, if busi- ness volume indicators were "number of ticket sales per quarter," or "monthly production of widgets," then the corresponding natural forecasting units would be "ticket sales" and "widgets." Natural fore- casting units are used by high-level executives to track the health of the overall business.
Business functions are a logical unit of work per- formed on behalf of a natural forecasting unit. For example, within an airline reservation system, a common business function might be "selling air- line tickets." This business function may consist of multiple interactions with the computer (e.g., flight inquiry, customer credit check). The comple- tion of the sale terminates the business function, and "airline ticket" acts as a natural forecasting unit for the enterprise selling the tickets. The measure- ment metric for business functions is the num- ber of business function occurrences per hour.
Business functions may be used by middle-level managers to track the activity of their departments.
A
transaction is an atomic unit of work for an application, and transaction response time is the primary performance measure seen by a user. Each of the interactions mentioned in the above busi- ness function is a transaction. The measurement metric for a transaction is the number of trans action occurrences per business function. Trans- actions may be used by low-level managers to track the activity of their groups.
The bulk of commercial applications involves the maintaining and moving of information. This information is data that is often stored on perma- nent storage devices such as rotational disks, solid state disks, or tapes.
An I/O operation is the process by which a transaction accesses that data. The mea- surement metric for the
I/O
profile is the number of
I/O
operations per transaction.
1 / 0 operations by each transaction are important to programmers or system analysts.
In addition to issuing VOs, each transaction requires a certain amount of
CPU
time to handle forms processing. (Forms processing time is not illustrated in Figure 1.) The measurement metric for forms processing time is the expected number of fields. The number of input and output fields per form are important metrics for users of a trans action processing application or programmer/ system analysts.
By collecting information about a transaction processing application at various levels, high-level volume indicators are mapped to low-level units of
I/O activity. This mapping is fundamental to the transaction processing sizing methodology.
60
VoL
3
No.
1
Winter I991 Digital TecbnicalJou+nal
Tools and Techniques for Preliminary Sizing of Transaction Processing Applications
Performance goals play a particularly important role in the sizing of transaction processing systems."
The major categories of performance goals com- monly encountered in the transaction processing marketplace are bounds for
Device utilization(s)
Average response time for transactions
Response time quantiles for transactions processor utilization of less than 70 percent. Such a constraint reflects the fact that system response time typically rises dramatically at higher proces- sor utilizations. A common performance goal for response time is to use a transaction's average response time and response time quantiles. For example, the proposed system should have an aver- age response time of x seconds, with
95
percent of all responses completing in less than or equal t o y seconds, where x is less than y. Transaction response times are crucial for businesses. Poor response times translate directly into decreased productivity and lost revenues.
When a customer generates a formal Request For
Proposal (RFP), the performance goals for the transaction processing system typically are speci- fied in detail. The specification of goals makes it easier to define the performance bounds. For customers who supply only general performance goals, it is assumed that the performance goal takes the form of bounds for device utilizations.
Overall response time consists of incremental contributions by each major component of the overall system:
Front-end processor
=
Back-end processor
Communications network
Disk subsystem
A main objective in this approach to sizing was to identlfy and use specific metrics that could be easily counted for each major component. For instance, the number of fields per form could be a metric used for sizing front-end processors because that number is specific and easily counted.
As the path of a transaction is followed through the overall system, the units of work appropriate for each component become clear. These units become the metrics for sizing that particular component.
The focus of this paper is on processor sizing with bounds on processor utilization. Processors gener- ally constitute the major expense in any proposed system solution. Mistakes in processor sizing are very expensive to fix, both in terms of customer satisfaction and cost.
Sizing Metrics
Transaction processing applications permit a large number of users to share access to a common data- base crucial to the business and usually residing on disk memory. In an interactive transaction process- ing environment, transactions generally involve some number of disk
I/O operations, although the number is relatively small compared t o those generated by batch transaction processing appli- cations.
CPU processing also is generally small and consists primarily of overhead for layered trans- action processing software products. Although these numbers are small, they did influence the sizing methodology in several ways.
Ratings for relative processor capacity in a trans- action processing environment were developed to reflect the ability of a processor to support disk
I/O activity (as observed in benchmark tests). In addition, empirical studies of transaction process- ing applications showed that, for purposes of pre- liminary sizing, the number of disk r/Os generated by a transaction provides a good prediction of the required amount of CPU processing Numerous industry-standard benchmark tests for product positioning were run on Digital's processors. These processors were configured as back-end proces- sors in a distributed configuration with different software platforms.
The base workload for this benchmark testing is currently the Transaction Processing Performance
Council's TPC Benchmark
A (TPC-A, formerly the set of benchmark testing was run under Digital's
VAX
ACMS transaction processing monitor and
\'Ax
RdblVMS relational database. Therefore, results from this software platform on all Digital proces sors were used to compute the first sizing metric called the base load factor.
The base load factor is a high-level metric that incorporates the contribution by all layered soft- ware products on the back-end processor to the total CPU time per
I/O
operation. Load factors are computed by dividing the total CPU utilization by the number of achieved disk
I/O operations per second. (The CPU utilization is normalized in the event that the processor is a Symmetrical Multi- processing
[SMP] system, to ensure that its value falls within the range of
0
to 100 percent.) The
Digital Technical Journal Vo1.3 No.
1 Winter 1991
6
1
Transaction Processing, Databases, and Fault-tolerant Systems
calculation of load factor yields the total
CPLJ time, in centiseconds (hundredths of seconds), required to support an application's single physical I/O operation.
The base Joad factors give the CPU time per I/O required to run the base workload, TPC-A, on any
Digital processor in a back-end configuration using the ~ c ~ s / R d b .
CPU time per
1/0 can be esti- mated for any workload. This generalized metric is called the application load factor.
To relate the base load factors to workloads other than the base, an additional metric was defined called the intensity factor. The metric calculation for the intensity factor is the application load factor divided by the base load factor. The value in using intensity factors is that, once estimated (or calculated for running applications), intensity fac- tors can be used to characterize any application in a way that can be applied across all processor types to estimate processor requirements.
Intensity factors vary based on the software platform used. If a software platform other than a combined
VAX
ACMS and
VAX
Rdb/VMS platform is selected, the estimate of the intensity factor must be adjusted to reflect the resource usage cliaracter- istics of the selected DECtp software platform.
To estimate an appropriate intensity factor for a nonexistent application, judgment and experience with similar applications are required. However, measured cases from a range of DECtp applications shows relatively little variation in intensity factors.
Guidelines to help determine intensity factors are included in the documentation for Digital's inter- nally developed transaction processing sizing tools.
The work required by any transaction pro- cessing application is composed of two parts: the application/database and the forms management.
This division of work corresponds to what occurs in a distributed configuration, where the forms pro- cessing is off-loaded to one or more front-end pro- cessors. Load factors and intensity factors are metrics that were developed to size the application/ database. To estimate the amount of CPU time required for forms management, a forms-specific metric is required. For a first-cut approximation, the expected number of (input) fields is used as the sizing metric. This number is obtained easily from the business-level description of the application.
Sizing Formulas
This section describes the underlying algebra devel- oped for processor selection. Different formulas to estimate the
CPU time required for both the application/database and forms management were developed. These formulas are used separately for sizing back-end arid front-end processors in a dis- tributed configuration. The individual contribu- tions of the formulas are combined for sizing a centralized configuration.
The application/database is the work that takes place on the back-end processor of a distributed configuration. It is a function of physical disk accesses. To determine the minimal CPU time required to handle this load, processor utilization is used as the performance goal, setting u p an inequality that is solved to obtain a corresponding load factor. The resulting load factor is then com- pared to the table of base load factors to obtain a recommendation for a processor type. To rein- force this dependence of load factors on processor types, load factor x refers to the associated pro- cessor typex in the following calculations.
One method for estimating the average
CPU time per transaction is to multiply the number of I/Os per transaction by the load factor x and the inten- sity factor. This yields CPU time per transaction, expressed in centiseconds per transaction. By mul- tiplying this product by the transactions per sec- ond rate, an expression for processor utilization is derivcd. Thus processor utilization (expressed as a percentage scaled between
0
and
100 percent) is the number of transactions per second, times the number of I/Os per transaction, times load factorx, times the intensity factor.
The performance goal is a
CIJU utilization that is less than the utilization specified by the customer.
Therefore, the calculation used to derive the load factor is the utilization percentage provided by the customer, divided by the number of transactions per second, times the number of I/Os per trans- action, times the intensity factor.
Once computed, the load factor is compared to those values in the base load factor table. 'The base load factor equal to or less than the computed value is selected, and its corresponding processor type, x, is returned as the minimal processor required to handle this workload.
The four input parameters that need to be esti- mated for inclusion in this inequality are
Processor utilization performance goal (tradi- tionally set at around 70 percent, but may be set higher for Digital's newer, faster processors)
Target transactions per second (which may be derived from Digital's multilevel mapping of business metrics)
Vo1.3 No.
1
Winter f99I
Digital
Technical Journal
Tools and Techniques for PreZi ;minary Sizing of Transaction Processing Applications
I/Os per transaction (estimated from application description and database expertise)
Intensity factor (estimated from experience with similar applications)
Note: Response time performance goals d o not appear in this formula. This sizing formula deals strictly with ensuring adequate processor capacity.
However, these performance parameters (includ- ing the
CpU service time per transaction) are fed into an analytic queuing solver embedded in some of the transaction processing sizing tools, which produces estimates of response times.
Forms processing is the work that occurs either on the front-end processor of a distributed config- uration or in a centralized configuration. It is not a function of physical disk accesses; rather, forms processing is
CPU intensive. To estimate the
Cpu time (in seconds) required for forms processing, the following simple linear equation is used:
y =
c(a
+
bz)
where y equals the
CPU time for forms processing;
a equals the CpU time per form per transaction instance, depending on the forms manager used; b equals the cpU time per field per transaction instance, depending on the forms manager used;
z
equals the expected number of fields; and c equals the scaling ratio, depending on the processor type.
This equation was developed by feeding the results of controlled forms testing into a linear regression model to estimate the
CPU
cost per form and per field (i.e., a and
6 ) .
The multiplicative term,
c,
is used to eliminate the dependence of factors a and
6
on the hardware platform used to run these tests.
Sizing Tools
Several sizing tools were constructed by using the above formulas as starting points. These tools dif- fer in the range of required inputs and outputs, and in the expected technical sophistication of the user.
The first tool developed is for quick, first- approximation processor sizing. Currently embod- ied as a DECalc spreadsheet, with one screen for processor selection and one for transactions-per- second sensitivity analysis, it can handle back-end, front-end, or centralized sizing. The first screen shows the range of processors required, given the target processor utilization, target transactions per second, expected number of fields, and the possible intensity factors and number of I/Os per transaction. (Because the estimation of these last two inputs generally involves the most uncer- tainty, the spreadsheet allows the user to input a range of values for each.) The second screen turns the analysis around, showing the resulting trans- action-per-second ranges that can be supported by the processor type selected by the user, given the target processor utilization, expected number of fields, and possible intensity factors and number of
I/Os per transaction.
The basic sizing formula addresses issues that deal specifically with capacity but not with per- formance. To predict behavior such as response times and queue lengths, modeling techniques that employ analytic solvers or simulators are needed.
A
second tool embeds an analytic queuing solver within itself to produce performance estimates.
This tool is an automated system (i.e., a DECtp application) that requests information from the user according to the multilevel workload charac- terization methodology. This starts from general business-level information and proceeds to request successively more detailed information about the application. The tool also contains a knowledge base of Digital's product characteristics (e.g., pro- cessor and disk) and measured DECtp applications.
The user can search through the measured cases to find a similar case, which could then be used to provide a starting point for estimating key applica- tion parameters. The built-in product characteris- tics shield the user from the numeric details of the sizing algorithms.
A
third tool is a spin-off from the second tool.
This tool is a standalone analytic queuing solver with a simple textual interface. The tool is intended for the sophisticated user and assumes that the user has completed the level of analysis required to be able to supply the necessary technical input param- eters. No automatic table lookups are provided.
However, for a completely characterized applica- tion, this tool gives the sophisticated user a quick means to obtain performance estimates and run sensitivity analyses. The complete DECtp software platform necessary to run the second tool is not required for this tool.
Data Collection
To use the sizing tools fully, certain data must be available, which allows measured workloads to be used t o establish the basic metrics. Guidance in sizing unmeasured transaction processing applica- tions is highly dependent on developing a knowl- edge base of real-world transaction processing application descriptions and measurements. The
Digital Tecbnical
Journal
%>I.
3
No. 1 Winter 1991
Transaction Processing, Databases, and Fault-tolerant Systems
kinds of data that need t o be stored
within the
knowledge base require the data collection tools to gather information consistent with the transaction processing sizing algebra.
For each transaction type and for the aggregate of all the transaction types, the following informa-
tion
is necessary t o perform
transaction
process- ing system
sizing:
CPU time per disk
I/O
Disk
I/O operations per transaction
Transaction rates
Logical-to-physical disk
I/O ratio
The CpU t o
I/O ratio can be derived from Digital's existing instrumentation products, such as the
V
S o h a r e Performance Monitor
(SPM) and VAXcluster
Performance Advisor
(VPA)
product^.^
Both prod- ucts can record and store data that reflects
CPU usage levels and physical disk
I/O rates.
The DECtrace product collects event-driven data.
It can collect resource items from layered soft- ware products, including
VAX
ACMS monitor, the
VAX
Rdb/VMS and
DBMS database systems, and if instrumented, from the application program itself.
As an event collector, the DECtrace product can be used to track the rate at which events occur.
The methods for determining the logical-to- physical disk
I/O ratio per transaction remain open for continuing study. Physical disk
I/O operations are issued based on logical commands from the application. The find, update, o r fetch commands from an
SQL program translate into from zero to many thousands of physical disk
I/O operations, depending upon where and how data is stored.
Characteristics that affect this ratio include the length of the data tables, number of index keys, and access methods used t o reach individual data items
(i.e., sequential, random).
Few tools currently available can provide data on physical
I/O operations for workloads in the design stage. A knowledge base that stores the logical-to-physical disk
I/O activity ratio is the best method available at this time for predicting that value. The knowledge base in the second sizing tool is beginning t o be populated with application descriptions that include this type of information.
It is anticipated that, as this tool becomes widely used in the field, many more application descrip- tions will be stored in the knowledge base. Pooling individual application experiences into one central repository will create a valuable source of knowl- edge that may be utilized t o provide better infor- mation for future sizing exercises.
Acknowledgments
The authors would like t o acknowledge our col- leagues in the Transaction Processing Systems
Performance Group whose efforts led to the devel- opment of these sizing tools, either through prod- uct characterization, system support, objective critique, o r actual tool development. In particular, we would like t o acknowledge the contributions made by Jim Bouhana t o the development of the sizing methodology and tools.
References
1.
W
Zahavi and J. Bouhana, "Business-Level Des- cription of Transaction Processing Applications,"
CMG
'88
Proceedings (1988): 720-726.
2. K.
Omahen, "Practical Strategies for Config- uring Balanced Transaction Processing Systems:'
IEEE COMPCON
Spring '89 Proceedings (1989):
554-559.
3.
W;
Zahavi, "A First Approximation Sizing
Technique -The
I/O
Operation as a Metric of
CPU Power,"
CMG
(forthcoming December 10-14,1990).
4.
"TPC BENCHMARK
A
-
(Transaction Processing Performance Council,
November 1989).
5.
"A
Measure of Transaction Processing Power,"
Datamation, vol. 31, no. 7 (April 1, 1985): 112- 118.
6.
L. Wright,
W
Kohler, and
W
Zahavi, "The Digital
Debitcredit Benchmark: Methodology and
Results,"
CMG
'89 Conference Proceedings
(1989): 84-92.
7.
E
Habib,
Y.
Hsu, and K. Omahen, "Software
Measurement Tools for VAXNMS Systems,"
CMG
Transactions (Summer 1988): 47-78.
Vol.
3 No.
1
Winter
1991
Digital Technical
Journal
डाउनलोड
विज्ञापन