Access Millions of academic & study documents

Discussion Question

Content type
User Generated
Showing Page:
1/6
Load Testing , Database application performance
1. 
2. 
3. 
4. 
5. 
6.  !
7. "#$
8. %&'$
Step 1 - Identify Performance Acceptance Criteria
Identifying performance acceptance criteria is most valuable when initiated early in the
application’s development life cycle. It is frequently valuable to record the acceptance criteria for
your application and store them in a place and format that is available to the entire team for
review and comment. Criteria are typically determined by balancing your business, industry,
technology, competitive, and user requirements.
Test objectives frequently include the following:
#()*+$$,
(
-$$()*+$$..
(
#$$'(&/$$
$$$+++
$$$0123+12(
4*$$(-,5$$
!!$(
6$(-,5,$$
$7*+$,8
(
Step 2 - Identify Key Scenarios
Scenarios are anticipated user paths that generally incorporate multiple application activities.
Key scenarios are those for which you have specific performance goals, those considered to be
high-risk, those that are most commonly used, or those with a significant performance impact.
The basic steps for identifying key scenarios are.
1. 9,()*+
,$$$:
6
$
;
1. ()*+<;
2=$:
>(
6$(

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/6
!$(
&(
?(
1. *$$
7,$()*+
+,,
*$+,$
,$,(
-*$*9,
,,*!(
-*$9,
,,+++(
#$,!,$
$$(-$:
;
4
12
@12
Once they have been identified, you will use these key scenarios to create workload profiles and
to design load tests.
Step 3 - Create a Workload Model
When defining workload distribution, consider the following key points for determining the
characteristics for user scenarios:
&$!+$
+,$(-,$
$(
&$$,$(-
user delay think time(
&$$$(
$!
$$+$+$$(
@,,$+$$+7
$*$$,(
Step 4 - Identify Target Load Levels
Identify the load levels to be applied to the workload distribution(s) identified during the previous
step. The purpose of identifying target load levels is to ensure that your tests can be used to
predict or compare a variety of production load conditions. The following are common inputs
used for determining target load levels:
6$$0,$53$
,5
A
,$
0+$+$3

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/6

Sign up to view the full document!

lock_open Sign Up
End of Preview - Want to read all 6 pages?
Access Now
Unformatted Attachment Preview
Load Testing , Database application performance 1. Step 1 - Identify performance acceptance criteria 2. Step 2 - Identify key scenarios 3. Step 3 - Create a workload model 4. Step 4 - Identify the target load levels 5. Step 5 - Identify metrics 6. Step 6 - Design specific tests 7. Step 7 - Run tests 8. Step 8 - Analyze the results Step 1 - Identify Performance Acceptance Criteria Identifying performance acceptance criteria is most valuable when initiated early in the application's development life cycle. It is frequently valuable to record the acceptance criteria for your application and store them in a place and format that is available to the entire team for review and comment. Criteria are typically determined by balancing your business, industry, technology, competitive, and user requirements. Test objectives frequently include the following: Response time.?For example, the product catalog must be displayed in less than 3 seconds. Throughput.?For example, the system must support 100 transactions per second. Resource utilization.?A frequently overlooked aspect is the amount of resources your application is consuming, in terms of processor, memory, disk input output (I/O), and network I/O. Maximum user load.? This test objective determines how many users can run on a specific hardware configuration. Business related metrics.?This objective is mapped to business volume at normal and peak values; for example, the number of orders or Help desk calls handled at a given time. St ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.
Studypool
4.7
Indeed
4.5
Sitejabber
4.4