Building an effective 80/20 performance testing for antique applications Chithira Selvan– Project Manager Senthil Kumar S & Associate Cognizant Technology Solutions

Abstract The Performance of the system plays a vital role in any huge software application. The software should be tested to check the Performance in speed, steadiness and scalability. Nowadays the primary objective of the Performance testing is to uncover what needs to be improved before the product goes to the market and this will determine whether or not their software meets all the performance requirements under unexpected workloads. Legacy applications are still supported by most of the business which exists for a long period of time. These antique applications as they continue to serve the critical business needs, they also have to transition to latest technology stack. In this transition Performance of application has to be considered as important parameter. In a trending market the performance/load/stress testing is not to find defects, instead we have to reduce blockages and create a baseline for further testing. There are legacy applications which perform millions of transactions per day and results out of those transaction .For these systems various performance parameters has to be considered for accuracy. However identifying crucial test scenarios and load distribution across the breadth of the application is one of the major actions of a performance test. It is very challenging to build and replicate in a test environment an exact model of the workload that the legacy application will be expected to process in production. With these objectives, we appropriated an effective way of carrying out 80/20 performance testing for antique applications. Here 80 % of the legacy application workload is generated by 20% of the new/old system functionality. In this method the capacity of the application will be determined along with 20% of the functionality which causes the major workload. Once workload approximation has been determined and agreed, the performance team will work towards constructing the automation into a workload that can be implemented in an orderly and controlled fashion. In concise, a Well-tuned legacy application has to follow a white box approach to spot inadequacies, database-specific profilers, operating system level and network level so that the application performance bottleneck is detected and resolved.

Application Overview Every minute of every day, our Client create millions of media moments all over the world. Largest broadcaster provides Scalable and Efficient Media Sales Solution, Creates and Delivers Efficient Ad Sales Campaigns for Linear TV and VOD Drives up Ad Revenue through Efficient use of Airtime and Controls Operational Costs in Ad Sales Teams through Automated Tools New State of the Art User Interface Drives Effectiveness Through Usability, Navigation, Notification and Inbuilt Data Analytics in Every Functional Area

Performance Testing

Problem Statement There are many antique applications continue to serve the critical business needs, they also have to transition to latest technology stack. In this transition Performance of application has to be considered as important parameter. These legacy applications performs millions of transactions per day. Identifying crucial test scenarios and load distribution across the breadth of the application is one of the major actions of a performance test. It is very challenging to build and replicate in a test environment an exact model of the workload that the legacy application will be expected to process in production.

Proposed Approach We appropriated an effective way of carrying out 80/20 performance testing for antique applications. Here 80 % of the legacy application workload is generated by 20% of the new/old system functionality. In this method the capacity of the application will be determined along with 20% of the functionality which causes the major workload. Once workload approximation has been determined and agreed, the performance team will work towards constructing the automation into a workload that can be implemented in an orderly and controlled fashion.

Key Test Scenario Selection It is not feasible to load test every transaction\Business Process Identify transactions that are: Data intensive High Volume Mission Critical Apply 80/20 approach to identify key performance scenarios Typically 20% of the new/old system functionality will generate 80% of the load on a system so not all transactions needs to be represented.

Work Smart on Right Things 80 % of the legacy application workload is generated by 20% of the new/old system functionality

Pareto Chart Monitored the client database transactions for a day. This clearly indicates that more load was give to the modules ‘Schedule’ and ‘Rights’

Benefits Focus to target on key work load areas Eliminates performance scoping on low risk areas. More Efficient More ideal for antique applications Approach allows to focus on key risk areas first

Author Biography Chithira Selvan works as a Project Manager at Cognizant Technology Solution, Chennai and have 10 years of experience in large scale Broadcasting domain, Communications and Data Analysis. She holds a Master’s Degree in Computer Applications. She is certified in ISTQB and CSQA Co-Author Biography Senthilkumar S works as a Associate at Cognizant Technology Solution, Chennai and have 7 years of experience in Broadcasting domain. He holds a Masters Degree in Computer Applications. He is certified in ISTQB and Six Sigma Green Belt Practitioner.

Thank You!!!