Prevent Web Performance Land Mines

  • 298 views
Uploaded on

Performance is a critical business issue. Research has shown that 75% of users will go to a competitor if your web performance is poor. Sites often bog down or fail during peak traffic times, exactly …

Performance is a critical business issue. Research has shown that 75% of users will go to a competitor if your web performance is poor. Sites often bog down or fail during peak traffic times, exactly when they need to perform at their best. Testing your site under realistic load is the only way to uncover and eliminate the performance landmines before they cost you sales and customers.

Listen to Andreas Grabner Compuware Technology Strategist, in order to learn:

• How top eCommerce business’s prepared themselves for the holiday season.
• How they made sure that peak holiday traffic would not take their site down.
• What the Top Performance LandMines that typically end up in a production environment are and how to avoid them

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
298
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Top Performance Land Mines (and how to address them)Andreas Grabner, Lead of Compuware Center of ExcellenceStephen Pierzchala, Technology Strategist, Compuware Center of Excellence
  • 2. WHY do WE care?
  • 3. OnlineGraduatePrograms.com “Instant America”
  • 4. OnlineGraduatePrograms.com “Instant America”
  • 5. OnlineGraduatePrograms.com “Instant America”
  • 6. OnlineGraduatePrograms.com “Instant America”
  • 7. OnlineGraduatePrograms.com “Instant America”
  • 8. OnlineGraduatePrograms.com “Instant America”
  • 9. WHAT do WE miss?
  • 10. Performance Land Mines found in Production• Bloated Web Frontends • Deployment mistakes• Too many Database • Traffic estimates incorrect Statements • Poorly provisioned hardware• Too heavy logging and tracing • No consideration of end user• Synchronized to Death devices or latency• Too chatty on remoting • Misconfigured CDN channels • Load Balancing Issues• Wrong use of O/R Mappers • Networking/infrastructure• Memory Leaks issues • Problematic 3rd parties
  • 11. Problem #1: Page Complexity
  • 12. Watch your Weight (Content Size) Avg Bytes # of Objects Avg GPSI 400,000 50 45 350,000 40 300,000 # of Objects/Avg GPSI 35 250,000 30Bytes 200,000 25 20 150,000 15 100,000 10 50,000 5 0 0 May Jun Jul 11 Aug Sep Oct Nov Dec Jan Feb Mar Apr 11 11 11 11 11 11 11 12 12 12 12
  • 13. Watch your Weight (Content Size) Avg Bytes # of Objects Avg GPSI 400,000 50 45 350,000 40 300,000 # of Objects/Avg GPSI 35 250,000 30Bytes 200,000 25 20 150,000 15 100,000 10 50,000 5 0 0 May Jun Jul 11 Aug Sep Oct Nov Dec Jan Feb Mar Apr 11 11 11 11 11 11 11 12 12 12 12
  • 14. Where did all of this stuff come from?(Application Complexity) Average number of hosts accessed by the browser across the Gomez US Sports Web Performance Benchmark 29
  • 15. Where did all of this stuff come from?(Application Complexity)Average number of hosts accessed by the browser across the Gomez USSports Mobile Website Performance Benchmark 12
  • 16. Cost of Complexity – 1
  • 17. Cost of Complexity – 1 As the page gets larger, it gets slower and more complex
  • 18. Cost of Complexity – 2 Response Time and Page Size by Hosts 16 3000000 14 2500000 12 2000000 10Seconds Bytes 8 1500000 6 1000000 4 500000 2 0 0 1 3 5 7 9 25 39 11 13 15 17 19 21 23 27 29 31 33 35 37 41 43 45 47 49 51 53 Hosts Geometric Mean BYTES
  • 19. Cost of Complexity – 2 Response Time and Page Size by Hosts 16 3000000 14 2500000 12 2000000 10 As the page gets moreSeconds complex, it gets slower Bytes 8 1500000 6 and larger 1000000 4 500000 2 0 0 1 3 5 7 9 25 39 11 13 15 17 19 21 23 27 29 31 33 35 37 41 43 45 47 49 51 53 Hosts Geometric Mean BYTES
  • 20. Tips for Production: Continuously monitor PageComplexity
  • 21. Tips for Production: Continuously monitor PageComplexity Reducing complexity produces a dramatic response time improvement
  • 22. Tips for Testing: Analyzing Page KPIs • Analyze Key Performance Indicators (KPIs) for every tested pageTested Pages KPIs
  • 23. Tips for Testing: Comparing Test Runs
  • 24. Problem #2:Slow 3rd Party Content
  • 25. 3rd Party Content is important
  • 26. Tips For Testing: Optimize your 3rd Party Content
  • 27. Tips For Testing: Optimize your 3rd Party Content
  • 28. Tips For Production: Monitor 3rd Party Impact
  • 29. Which 3rd Party Provider is your Hotspot?
  • 30. Is it Load related? Does it impact everybody?
  • 31. Monitor 3rd Party Content over time
  • 32. Monitor 3rd Party Content over time Not every host affects performance equally all the time
  • 33. Outage Analyzer Failures for a Single Day 40000 35000 30000 25000 20000 15000 10000 5000 0Compuware Outage Analyzer Results, October 2012
  • 34. Problem #3:Deployment Issues
  • 35. Top Deployment Problems• Missing Files• Incorrect Access Settings• Slow Web Server Modules
  • 36. (1) Missing Files: Impact User Experience Enter Here PopUp Here
  • 37. (1) Missing Files: Lead to JavaScript Errors Errors caused by missing files
  • 38. (1) Missing Files: How to identify• Watch out for HTTP 4xx
  • 39. (1) Missing Files: Tips for Testing• Test with real browsers – HTTP-only testing might not download dynamically loaded JS files – Catch browser-specific implementations• Test from the In- and Out-side – Files might be deployed on AppServer but blocked on Web Server or Load Balancer – Certain files might come from a CDN. Testing the CDN settings is important
  • 40. (2) Incorrect Access Settings: Impact User Experienceand Performance 14k Errors in 5 minutes after deploying in Production
  • 41. (2) Incorrect Access Settings: Impact User Experienceand Performance Deployment causes extra roundtrips for each restricted resource
  • 42. (2) Incorrect Access Settings: Tips for Testing• Test with real browsers – HTTP-only testing might not download dynamically loaded JS files – Catch browser-specific implementations• Test from the In- and Out-side – Files might be accessible on AppServer but blocked on Web Server – Watch out for missing JS, CSS and Image files
  • 43. (3) Slow Web Server Modules: Performance Impact• 90% of ASP.NET Request Time spent in IIS 90%
  • 44. (3) Slow Web Server Modules: Tips for Testing• Test with all Modules used in Production• Analyze Time spent in Modules vs. Application Code
  • 45. Resources• Free Online Java Enterprise Performance Book – http://javabook.compuware.com/• Our Performance Blog – http://apmblog.compuware.com• Contact – Andreas Grabner • andreas.grabner@compuware.com • @grabnerandi – Stephen Pierzchala • stephen.pierzchala@compuware.com • @spierzchala
  • 46. THANK YOU