The High Performance Web Application Lifecycle
•
4 j'aime•711 vues
This document discusses high performance web application lifecycles. It covers trends in continuous integration, automated web performance testing, and continuous monitoring in production. Metrics like page load time, resource timing, and third party content load time are discussed. The document also covers browser APIs like Navigation Timing and Performance Timeline that provide performance metrics, and how these can be used to analyze performance across builds and detect common problems. Limitations include lack of support in older browsers and inability to provide insight into JavaScript.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (15)
Similaire à The High Performance Web Application Lifecycle
Similaire à The High Performance Web Application Lifecycle (20)
Plus de Alois Reitbauer
Plus de Alois Reitbauer (20)
Dernier
Dernier (20)
The High Performance Web Application Lifecycle
- 1. High Performance Web Application Lifecycle Alois Reitbauer, Technology Strategist Compuware
- 2. about:me Alois Reitbauer Technology Strategist, Compuware @AloisReitbauer alois.reitbauer@compuware.com
- 3. We all know the “basics”
- 4. Trend in Web page size
- 5. Continuous Continuous Integration Continuous Monitoring
- 8. Ensure tracing is started with your tests <target name="test"> <junit fork="true" haltonfailure="true"> <test name="com.dynatrace.ajax.selenium.SimpleTest" /> <env key="DT_AE_AGENTACTIVE" value="true" /> <env key="DT_IE_AGENTNAME" value="SimpleTest" /> <env key="DT_IE_SERVERPORT" value="9988" /> </junit> </target>
- 9. Configure automatic test result upload -Dcom.dynatrace.diagnostics.ajax.beacon.autoupload= true -Dcom.dynatrace.diagnostics.ajax.beacon.uploadurl= http://localhost:8080/beaconstorage/endpoint/ -Dcom.dynatrace.diagnostics.ajax.beacon.portalurl= http://localhost:8080/beaconstorage/dashboard.html
- 10. Analyze Performance across Builds
- 12. Does this really work?
- 14. The Good Parts For free with functional tests Provides immediate feedback Detects most common problems To keep in mind Timings not necessarily accurate “Real World” Deployment is best Needs cultural support
- 16. A typical eCommerce Page
- 17. ... now without external dependencies # of # of Total DNS Connect Domains Resources Bytes [ms] [ms] With Third Party Content 26 176 2856 Kb 1286,82 1176,09 Without Third Party 2 59 897 Kb 0,91 22,25 Content
- 18. How to get this metrics for our users?
- 19. onLoad Time Measurement <html> <head> <script type="text/javascript"> var start = new Date().getTime(); function onLoad() { var now = new Date().getTime(); var latency = now - start; alert("page loading time: " + latency); } </script> </head> <body onload="onLoad()"> ……
- 20. Resource Time Measurement …… <script type="text/javascript"> downloadStart(“myimg”); </script> <img src=“./myimg.jpg” onload=“downloadEnd(„myimg‟)” /> …..
- 22. Web performance specifications • Navigation Timing Timing Information on Page Loading • Resource Timing Performance information on individual resources. • User Timing Custom user actions or specific timings e.g.: getting a search result • Performance Timeline Unified API for accessing all this information
- 24. Works in many browsers http://blog.dynatrace.com/samples/bookmark.html
- 26. The Good Parts Very detailed timing information “No”effort to get data Easy to find network-based problems To keep in mind Not supported in older browsers Safari is not supported No JavaScript insight
- 27. Polyfilling for older browsers Page Load Time Resource loading (except JS & CSS) also works in Safari Insight into JavaScript executions Browser Error Reporting Merge with “classical” analytics data
- 28. Cool stuff you can do with this
- 30. Third Party Content Monitoring
- 31. Screen size impact on rendering
- 32. Putting it all together
- 33. 33 © 2011 Compuware Corporation — All Rights Reserved
Notes de l'éditeur
- url parameter zumabschalten der einzelnenseitenelemente