Case study on Performance Profiling of Software for Financial Services
0 likes746 views
The document details a case study on performance profiling for a web-based financial product by Oak Systems Pvt. Ltd., focusing on ensuring high response times and minimal degradation under load. Various testing methodologies such as concurrency, stress, and throughput testing were discussed, along with the test environment and sample test cases. The company aimed to evaluate performance metrics and improve performance characteristics through appropriate testing strategies.
Case study on Performance Profiling of Software for Financial Services
- 1. Case StudyCase Study Performance ProfilingPerformance Profiling
- 2. 1/5/03 Oak Systems Pvt. Ltd. 2 BackgroundBackground •• A Web based Financial productA Web based Financial product •• High response time was expected due to GlobalHigh response time was expected due to Global reach of services offeredreach of services offered
- 3. 1/5/03 Oak Systems Pvt. Ltd. 3 General Performance ProfilingGeneral Performance Profiling •• Concurrency : Concurrency testing seeks to validateConcurrency : Concurrency testing seeks to validate the performance of an application with a giventhe performance of an application with a given number of concurrent interactive usersnumber of concurrent interactive users •• Stress : Stress testing seeks to validateStress : Stress testing seeks to validate performance when certain aspects of applicationperformance when certain aspects of application are stretched to their maximum limitsare stretched to their maximum limits •• Throughput : Throughput testing seeks to validateThroughput : Throughput testing seeks to validate number of transactions to be processed during anumber of transactions to be processed during a given period of time.given period of time.
- 4. 1/5/03 Oak Systems Pvt. Ltd. 4 Client’s Project GoalsClient’s Project Goals •• Fast response timeFast response time •• Marginal degradation in performanceMarginal degradation in performance with increasing loadswith increasing loads
- 5. 1/5/03 Oak Systems Pvt. Ltd. 5 Test environmentTest environment (Designed by OAKSYS)(Designed by OAKSYS) » A server with Application S/w Loaded, up and running in simulated production environment » An Application Server » A Web server » A Server with database installed and connected to the application » A separate server with Performance testing tool » A PC (client) with typical client setting for simulating all the ‘X’ no. of Virtual Users (VU) hitting the server from that client
- 6. 1/5/03 Oak Systems Pvt. Ltd. 6 Sample test casesSample test cases •• Measuring the Response time (at differentMeasuring the Response time (at different transmission rates) with load varying fromtransmission rates) with load varying from 100100 -- 1000 Virtual Users (VU) in increments of1000 Virtual Users (VU) in increments of 100 VU100 VU •• Measuring VU load for performanceMeasuring VU load for performance degradation in response timedegradation in response time •• Scalability test for peak and offScalability test for peak and off--peak responsepeak response time with incremental Virtual user simulationtime with incremental Virtual user simulation and incremental volume of Database sizeand incremental volume of Database size
- 7. 1/5/03 Oak Systems Pvt. Ltd. 7 Metrics CollectedMetrics Collected •• Hits Per SecondHits Per Second •• Hit TimeHit Time •• Response TimeResponse Time •• ThroughputThroughput ––And many more…And many more…
- 8. 1/5/03 Oak Systems Pvt. Ltd. 8 Our Value AddOur Value Add •• Determining test cases for testing the projectDetermining test cases for testing the project goalsgoals •• Usage of an appropriate Load testing tool forUsage of an appropriate Load testing tool for measuring the performance characteristicsmeasuring the performance characteristics •• Designing Test environmentDesigning Test environment •• Useful metrics collectionUseful metrics collection •• Ownership of performance testsOwnership of performance tests