1. BMC Remedy ITSM Performance Testing Case Study using Vyom Performance Test Edge for Capgemini

2. Why Performance Testing?
Mainly to gauge system stability and system responsiveness.
To identify potential performance problems and to provide recommendations to address those.
To identify a performance baseline for subsequent migrations.
Business activities that warrant performance benchmark tests
New Application Implementation
Capacity Planning
Upgrade
Anticipated increase in user or data load
Periodic system check
Workload is based on:
Rate of business transactions
Number of users carrying out those transactions

3. Performance Testing - Load Estimation
Transactions can be broadly classified as create/update/search
Let us say, that you identified your peak load as 420 create transactions, 900 update transactions and search transactions
Assuming that a test-case can be run in a minute, table below shows minimum number of users you need to achieve the transactional workload
Number of users in the above table is equivalent to:
Number of Threads in Vyom Test Edge
Called as Virtual Users by certain tools
Test Case
Peak Load/hr
Test Duration (minutes)
Max Number of Executions/user/hr
Minimum No. of users
Create
420 1 60 7
Update
900 15
Search
1200 20

4. Performance Test Scenarios
Test scenarios are hypothetical use cases on which scripts for performance benchmarking tests are based, while developing test scenarios follow following guidelines:
Choose typical business transactions and imitate real-life usage.
Write a script for each scenario.
Pre-populate transaction data.
Parameterize user input.
Include wait times.
Test scripts thoroughly.

5. Performance Testing using Vyom Test Edge Setting Workload
No. Of Users
Initial Delay
Startup Time (minutes)
Hold Time (minutes)
Shutdown Time (minutes) 25 10 60

6. Performance Testing using Vyom Test Edge Workload
Typically we run the Test-Suite for following workloads:
1 hr 100% peak-load (this is a dry-run or smoke-test)
24 hr 100% peak-load
24 hr 125% or 150% peak-load
2 hr 200/250% peak-load
For pre-populating data, you can use existing test-scripts bundle them up in a new project and run it prior to main test for appropriate time.

7. Performance Testing using Vyom Test Edge
We support ARS versions, and 8.X
You just have to select appropriate HTTP Sampler type while recording your scripts as shown below:

8. Testing Done for Capgemini
The scope of this ‘Performance Testing Activity’ involved testing the performance of Capgemini’s India and Paris instances, benchmarking the India instance.
Testing was carried out on the Production Server located in India (off-peak hours) and UAT Environment located in Paris for the version ITSM 8.1 SP2, to analyze the behavior with an increased workload 1000 concurrent users.
India and Paris Instance-15minutes, 1 user test run.
India and Paris Instance- Long duration 4 hour test run, 1000 concurrent users.

9. Test Scripts - Activities Performed by the Users
Create Incident
Search and Update Incident
Create Work Order
Search and Update Work Order
Create Service Request (Type: Work Order)
Create Service Request (Type: Incident)

10. Reporting
One of the most important aspects of performance testing engagement is the performance testing report. Stakeholders, managers need more than simply the results from various tests — they need conclusions based on those results, and data supporting those conclusions.
We report End-user response times, resource utilizations, volumes, capacities, and rates, component response times and trends.

11. Sample Graph - 1
Active Threads Over Time

12. Sample Graph - 2
Performance Monitor (CPU + Memory)

13. Sample Graph-3
Response Time Percentile

14. Sample Graph-4
Response Time Percentile (Saving an Incident)

15. Sample Graph-5
Response Time Distribution (Saving an Incident)

16. Q & A

17. Thank You! Email : chaitali.patwa@vyomlabs.com
Website :