AtlasCamp 2013: Show Me Number! Automated Browser Performance Testing

  • Published on
    06-May-2015

  • View
    183

  • Download
    0

Embed Size (px)

Transcript

  • 1.@atlassian #atlascamp

2. Show Me the Numbers Automated Browser Performance TestingChris Mountford Senior Software Developer, JIRA Atlassian @chromosundrift 2 3. Chris Mountford2005 3.4.1 185 16660 3 4. Chris Mountford4 5. Chris Mountford4 6. Chris Mountford Inline Edit4 7. Chris Mountford Inline Edit4 8. Chris Mountford Inline EditSearch4 9. Chris Mountford Inline EditSearch4 10. Chris Mountford Inline EditSearch Detail View 4 11. Chris Mountford Inline EditSearch Detail View 4 12. Browser Performance Testing Welcome! 13. Browser Performance Testingof specic interactions for a single user Measuring theperceived performance 6 14. Browser Performance Testingof specic interactions for a single user Measuring theperceived performance perceived 7 15. Outline Intro Optimisation Techniques JavaScript Renaissance Engineering Perception Performance Factors Gotchas Take Aways JIRA Perf Tests8 16. Outline Intro Optimisation Techniques JavaScript Renaissance Engineering Perception Performance Factors Gotchas Take Aways JIRA Perf Tests8 17. JavaScript Timeline A history lesson 18. 1995Classical JavaScript10 19. Browser Wars10 20. Browser WarsDark Ages10 21. Dark AgesFirebug10 22. V8Firebug10 23. V8Node.jsFirebug10 24. Node.jsHipsters10 25. 11 26. 12 27. 13 28. Why do we split everything into so many files?13 29. Why do we split everything into so many files?Performance. 13 30. 14 31. Why do we merge all the files into large batches?14 32. Why do we merge all the files into large batches?Performance. 14 33. 15 34. Why...15 35. Why...Performance! 15 36. Why...Performance! 15 37. Show me the numbers! Not Jacky ChanHey its Jacky16 38. If all we have are opinions, lets go with mine. If we have data, lets look at data.Netscape CEO Jim Barksdale17 39. Factors That Influence Browser Performance sad panda 40. Mobile Web Everything is the same but worse network / radio power mode steps, sleep, etc. cpu / battery impact memory standards compliance tooling 19 41. Network Time 20 42. Parse Time 21 43. JavaScript Execution JS Engines native bind(), map() etc DOM Manipulation events JQuery Sizzle selectors micro-optimisation Memory leaks22 44. Blocking23 45. Blocking