The document discusses performance analysis of a large intranet web application called Global Projects Delivery (GPD) which was experiencing erratic response times for users. Key findings from the analysis were: 1) Most traffic occurred during morning, post-lunch, and evening peaks and was concentrated on a few frequently accessed pages like daily task updates. 2) While the application server response time was good, 98% of the total response time was spent on data transfer, indicating the network was the bottleneck. 3) Pages with multiple frames and requests slowed down data transfer rates significantly compared to simpler pages. 4) Actions recommended included redesigning pages to reduce frames and requests, relocating servers closer to users, and

1. Application Performance Analysis Finding Bottlenecks in End-user Experience of Applications

5. Capture All the Elements – Fish Bone Diagram GPD

7. Large Intranet Web Application Case Study ..

9. GPD Architecture Overview Web Layer /IIS HTTP/HTT COM Components Services Layer ASP ASP ASP Messaging/ Mail Extraction Business Processing Validation Graphs/ Charts Query/ Report Building MS Project Utility Active Report Server Microsoft Project Pinnacle Graphic Server Microsoft CDONTS SQLServer Data Access Layer ADO Report Browser

11. Probes – Onion Ring formation for differential Analysis. Based on the network and system design given by Company-X, we planned to deploy 12 probes over different layers of the infrastructure

13. Typical Internet Transaction Where is the server? DNS resolution Client Identifies server Connect to server with request (GET) Client connects to server Server Response with Initial byte of data Includes Web server Application Server Database .. Server responds With request Time to download data fully Including Page Layout Page objects .. images frames (which form requests) Page content Request is transmitted to the client

15. Page wise analysis - 8 pages constitute 80% of hits … Selected as the Target Pages in the Test Environment 7.5% others 0.6% PM/DetailsDA.asp 0.7% IBIsEntForRvw.asp 0.8% IB/IBQueryBld.asp 1.0% PM/ProjectRES.asp 1.1% EmployeeSel.asp 1.1% PMDashboard.asp 1.4% ReportUIBld.asp 3.2% IBIssueAssgn.asp 3.3% DailyActivityMatrix.asp 4.1% CommonPage.asp 5.3% DeveloperDatabase.asp 7.0% Introduction.asp 7.0% IBIssueList.asp 8.8% CommonList.asp 47.2% DailyActivity.asp

17. In English! these key pages are 3.2% 3.3% 4.1% 5.3% 7.0% 7.0% 8.8% 47.2% Assign Work Request Task Up Date for a period Project Task List for User ?? Back end page that runs with login List Work Request Received Project List for logged user Task Up date IBIssueAssgn.asp DailyActivityMatrix.asp CommonPage.asp DeveloperDatabase.asp Introduction.asp IBIssueList.asp CommonList.asp DailyActivity.asp

22. 98% of response is in Data Transfer.. Server Response with Initial byte of data Includes Web server Application Server Database .. Server responds With request 98% 1.6% ~0% ~0% Where is the server? DNS resolution Client Identifies server Connect to server with request (GET) Client connects to server Time to download data fully Including Page Layout Page objects .. images frames (which form requests) Page content Request is transmitted to the client

23. 98% of response is regardless of location or time…. Overall SERVER IS NOT THE BOTTLE NECK

25. For e.g. in Common list & daily Activity the transfer time increases 3 – 5 X with more requests.

32. Actions from Discussion HI | Need to create the extra access HI | reduces data volume Create Separate portals for Managers & Users. Users could have frameless simple pages NIL MED : reduce multiple requests. LO : reduce redundant hits to server HI : reduce redundant hits to server HI : change design of pages HI : potential to improve data transfer speeds by multiples APPLICATION Reduce # of requests by reducing FRAMES; Images (not as critical) Improve presentation flow | Ensure users need fewer clicks to access important pages like daily Activity. Remove images on the pages GPD ; Company-X :hourglass HI : Consulting engagement HI : Identify specific device & design related issues Study and optimize data routing between clients and server HI : direct cost increase HI : More space less latency Introduce more bandwidth on to the pipe Lo : Efforts minimal but impact on other applications could be adverse. HI : More space less latency Increase Pipe Allocation from current burst max of 2 MB to 3 MB HI : move hub to server location MED : fewer hopes fewer drops Bring network HUB close to server location HI : need to relocate production server to BLR HI : reduces load on the link (2/3 users are in BLR & HYD >> free pipe by 50% traffic BRING SERVER CLOSER TO MASS OF USERS NETWORK EFFORT IMPACT ACTION