Performance Testing

-
There are 3 main concerns that performance testing seeks to address.
These concerns form the acceptance criteria or metrices for the tests.
They are:
  1. User concern – Response Time
  2. Business concern - Throughput. E.g. requests/ sec; calls/ day
  3. System concern - Resource Utilisation (often overlooked). E.g. processor & memory utilisation; disk I/O; network I/O

Purpose of Performance Testing

Depending on what has been done, performance testing helps in assessing:

  1. release readiness
  2. infrastructure adequacy
  3. software performance
  4. performance tuning efficiency

Some Definitions


  • Performance Target = Performance Goals
  • Performance Requirements = contractual obligation, SLAs that cannot be compromised. = Performance Thresholds
  • Workload = Stimulus applied. E.g. number of users, concurrent users, data volume, transaction volume.

Types of Performance Testing


  • Load Testing - testing within anticipated production load/ volume
  • Stress Testing - testing beyond expected production load/ volume. Objective is to reveal application bugs that will only surface under load. E.g. synchronisation issues, race conditions, memory leaks.

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

How to depict (Professional-Looking) Logical Network Diagrams in Astah

-
Image
I have always had to create (professional-looking) UML diagrams using Visio-like icons. You’ve got to admit that showing a bunch of boring UML boxes hardly interests anyone less technical (like anyone whose designation has the words “manager” or “director”). This is actually possible in Astah! I’ve created a template for future projects that allows me to produce logical network diagrams that look like the following: To create this diagram, you need to do the following: Assign various icons to stereotypes. I created the following for my use: Create a new UML Deployment Diagram Every element in the diagram is created as a Node The nodes are subsequently assigned the appropriate <<stereotype>>. E.g. Internet is <<internet>>, WebZone FW is <<firewall>>, Web LB is <<loadBalancer>> Ensure the “Icon Notation” is set to “Customized Icon” for each node Instead of the boring boxes, the corresponding icons automatically gets displayed!
Read more