Performance Testing
Ensure improved user experience with stable,
scalable, and responsive applications.
Performance Testing
Ensure improved user experience with stable,
scalable, and responsive applications.
Overview
Applications fail to meet the required outcomes and customer expectations when performance testing is not an integral part of the overall development lifecycle. We, at Intelliswift, provide services right from the design stage and make it an iterative process, so that the product is continuously improved upon while in development itself.
We ensure that the application is responsive and reliable to respond to peak loads and is aligned to future releases, regulatory changes, and ongoing business growth. We also ensure that the applications can meet any contractual obligations and SLAs for performance.
Key areas of focus
Speed
Does the application respond quickly enough for the intended users?
Scalability
Will the application handle the expected user load and beyond?
Stability
Is the application stable under expected and unexpected user loads?
Acceptability
Are you sure that users will have a positive experience on go-live day?
Performance Testing
Load/Benchmark Testing
- Perform Under Anticipated Load
- Compare with earlier version of SW/HW or competitor analysis
- Simulate real life usage pattern.
- Measure performance of Application under statistically representative load.
- Perform on UI/API/Mobile
Stress/Fatigue Testing
- Perform Under Extreme Load with Minimum Hardware/Requirement Support.
- Check the Environment stability
- To check response time is degraded, data is corrupted, security vulnerability is open or not, Check transaction loss after system fails.
- Perform on UI/API/Mobile
Endurance/Sock Testing
- Perform with expected load over long period of time
- Helps to check for memory leaks
- Perform on UI/API
Scale/Elasticity Testing
- Scale up/down as per the load
- Indicate threshold for upgrade requirements
- Measures peak load an application can handle without degrading the performance
- Perform on API/UI
Volume/Flood Testing
- Large No. of Data Testing
- Measures application, middleware, DB performance when data volume is high
- Batch/ETL/Data Analytics/Bulk Email
Our Approach
Requirement Gathering
- Gather performance requirements
- Identify critical business scenarios at UI, API and DB layer
- Define & agree on SLAs
- Identify concurrency load levels
- Performance Test and Monitoring Tool Selection
- Architecture & Design understanding
Test Planning & Design
- Prepare Test plan
- Prepare Workload Model
- Define Performance Test Scenarios
- Test Tool connectivity and verification
- Define Acceptance criteria & targets
- Identify test data dependencies
Scripting
- Creation of Test Scripts for identified flows using selected tool
- Create test data and clean up scripts
- Validate the test data
- Setup Monitoring counters on Servers
- Perform Dry run of the scripts
Execution
- Execute below tests with concurrent users
- Benchmark Test
- Load Test
- Stress Test
- Endurance Test
- Scalability
- Verify application logs and DB records in case of inserts and update scenario
- Monitor the resource usage using monitoring tools
Analysis & Tuning
- Analyze the metrics & stats
- Use Profiling tools for deep dive analysis
- Use Application Monitoring Tools
- Use application logs
- Identify bottlenecks
- Provide recommendations for tuning
- Benchmark the results
Reporting
- Publish interim test results
- Creation of Test Summary reports
- Trending reports against TPS/Throughput
- Ensure performance targets & SLAs are met
- Test result Sign-off
Performance
Readiness
Iterative & Multiple Runs
Publish and
Sign-off
Key Metrices (Indicative Sample Set)
Response Time
Total time to send the request and get the response.
Request per seconds
How many requests are handled.
Average Load Time
The average amount of time it takes to deliver every requests.
Peak Response Time
Measurement of the longest amount of time it takes to fulfill a requests.
CPU Utilization
How much time the CPU needs to process the requests.
Memory Utilization
How much memory is needed to process the requests.
Wait Time/Average latency
It informs the developers about the time it takes to receive the first byte after the request is sent.
Transaction Passed/Failed
Measure the total number of successful and Unsuccessful requests.
Throughput
Measured by Kilobyte per seconds, It shows the amount of bandwidth used during the test.
Error Rate
This calculation is percentage of request resulting in errors compared to all requests.
Concurrent User/Load Size
This is the most common measurement of the load and number of active users at any point.
How may I help you?
Welcome to Intelliswift Bot
IntelliBot
Support Agent
Hi, Welcome to Intelliswift!
I am here to help you find your way! What are you looking for?
What are you looking for?