1 © Mahindra Satyam 2009 Performance Testing as a Service using jMeter

2 © Mahindra Satyam 2009 Performance Testing Process Steps Completion of Testing Engagement Form Completion of Test Planning Questionnaire Test Planning Session Development of Performance Test Plan Development of Automated Test Scripts in pre-production Execution of Automated Test Scripts Identification of Performance Issues from test executions Resolution of Performance Issues Development of Test Summary Report

3 © Mahindra Satyam 2009 Performance Testing Process - Sample Timeline Engagement 1 week  Engagement Form  Design Review  Test Plan  Pre-Prod Review  MPC Schedule Planning 1 week Scripting  Script Writing 1 week Test Execution  Test Results  Production Review 3 weeks Test Reporting  Summary Test Report  Post Implementation Review 1 week The timelines will be tailored based on the complexity of the project and availability of the resources

4 © Mahindra Satyam 2009 Different Tests that are conducted Test NameTest ObjectiveUser Load Load TestTo test critical application functionality under peak user load Peak Concurrent Users Stress TestTo test critical application functionality under heavy user load 2x Peak Concurrent Users Endurance TestTo test critical application functionality under peak user load for a minimum of 8 hours Peak Concurrent Users Durability TestTo test application/hardware failover at all tiersPeak Concurrent Users Red Alert TestTo ensure modified application does not cause performance degradation on the Red Alert applications Peak Concurrent Users Breakpoint TestTo identify the maximum number of users the application will support TBD by test Sample Metrics collected : Transaction Performance Summary Transaction Response Time – Average Web Hits Per Second Web Server Throughput Average Load

5 © Mahindra Satyam 2009 Break Point Testing - Sample Break Point Testing (85 users – Break Point) Users Running: 85 Run time: 4 minutes Response time: > 7 sec Passed Transactions: 2354 Failed Transactions: 16 Error Rate:0.67% Hits/second: 33 Queries/Minute: 588 CPU Utilization, Memory Utilization : Not Applicable for the testing of the Break point for queries

6 © Mahindra Satyam 2009 Failover Testing - Sample Fail-Over Testing Criteria: Durability testing, also known as failover testing in other environments, is used to verify that the application continues to operate properly even when primary infrastructure and application, global, and external components fail. Furthermore, the application must continue to operate under load after the failure for the specified time period. Less than 1% is considered a passing result. Results: Web/app hard failover (shutdown server) Recovered in 15 second timeframe Response times: seconds Errors: 767 (.4%) Web/App soft failover (failover server software) Recovered in 15 second timeframe Response times: seconds Errors: 289 (.005%) Database soft failover (Failover to secondary node) Recovered in 60 second timeframe Response times: seconds Errors: 294 (.005%)

7 © Mahindra Satyam 2009 Web Services Performance Testing (SOAP UI) - Sample

8 © Mahindra Satyam 2009 Performance Testing – Sample screens

9 © Mahindra Satyam 2009 mahindrasatyam.net Safe Harbor This document contains forward-looking statements within the meaning of section 27A of Securities Act of 1933, as amended, and section 21E of the Securities Exchange Act of 1934, as amended. The forward-looking statements contained herein are subject to certain risks and uncertainties that could cause actual results to differ materially from those reflected in the forward-looking statements. Satyam undertakes no duty to update any forward-looking statements. For a discussion of the risks associated with our business, please see the discussions under the heading “Risk Factors” in our report on Form 6-K concerning the quarter ended September 30, 2008, furnished to the Securities and Exchange Commission on 07 November, 2008, and the other reports filed with the Securities and Exchange Commission from time to time. These filings are available at Thank you