Downloaded 10 times
![AsImPlEsImUlAtIoNShElLScRiPt
#!/bin/sh!
#!
# simulate_3g.sh - Simulate a sluggish 3G network with delays & packet loss!
# Usage: simulate_3g.sh 8080 8081!
!
# Make sure only root can run our script!
if [[ $EUID -ne 0 ]]; then!
echo "This script must be run as root" 1>&2!
exit 1!
fi!
!
# Simulate http over 3G, 300kbit/s with 5% packet loss and 200ms delays!
# into all ports given as a parameter!
ipfw pipe 1 config delay 200 plr 0.1 bw 300kbit/s!
for var in "$@"!
do!
ipfw add 1 pipe 1 dst-port $var!
done!](https://image.slidesharecdn.com/2013-10-02-html5-performance-aarhus-131008075256-phpapp02/85/2013-10-02-html5-performance-aarhus-19-320.jpg)
![AsImPlEsImUlAtIoNShElLScRiPt
#!/bin/sh!
#!
# simulate_3g.sh - Simulate a sluggish 3G network with delays & packet loss!
# Usage: simulate_3g.sh 8080 8081!
!
# Make sure only root can run our script!
if [[ $EUID -ne 0 ]]; then!
echo "This script must be run as root" 1>&2!
exit 1!
fi!
!
# Simulate http over 3G, 300kbit/s with 5% packet loss and 200ms delays!
# into all ports given as a parameter!
ipfw pipe 1 config delay 200 plr 0.1 bw 300kbit/s!
for var in "$@"!
do!
ipfw add 1 pipe 1 dst-port $var!
done!](https://image.slidesharecdn.com/2013-10-02-html5-performance-aarhus-131008075256-phpapp02/75/2013-10-02-html5-performance-aarhus-19-2048.jpg)
Uploaded bySC5.io
2013 10-02-html5-performance-aarhus
The document discusses the evolution of computing performance and web application development, highlighting significant advancements in CPU speed, display technology, and network bandwidth over 15 years. It stresses the need for web applications to be optimized for performance, addressing challenges such as loading times and resource management while comparing web apps to native apps. Additionally, it provides practical tips for optimizing web page load speeds and improving overall user experience through effective caching, resource combining, and understanding CSS and JavaScript performance impacts.
More Related Content
Similar to 2013 10-02-html5-performance-aarhus
2013 10-02-html5-performance-aarhus
- 1. HtMl5 eXpErTiSeaTyOuRsErViCe  LaUrISvAn@lAuRiSvAn Sc5OnLiNe @sC5 EnGiNeErInGHtMl5aPpLiCaTiOnS fOr bEtTeR pErFoRmAnCe
- 2.
- 3. 15YeArSReTrOsPeCtIvEoFMyPeRsOnAlGeAr 1000 tImEstHesPeEdiN15yEaRs  CPUDisplay Connection Network Speed / bps CPU / MFLOPS Pixels 1994 80486 640x480 modem 14,400 3 307,200 1999 AMD Athlon 500 1024x768 ISDN 128,000 180 786,432 2003 AMD Athlon Tbird 1600x1200 cable modem 300,000 373 1,920,000 2010 Intel Core i5 HDMI cable modem 4,000,000 4,256 4,096,000
- 4. 1000tImEs tHeCpU,20tImEstHeBaNdWiDtHtODrAw aPiXeL web  pages?  slow  web  pages!  pre.y   good  pages  (in  desktop) Â
- 5.
- 6.
- 7. WegOtuSeDToCrEaTiNgSlUgGiShWeBSeRvIcEs AttHeSaMetImE,ApPlEdElIvErEd aSlIcKApPExPeRiEnCe Äą7 2005  2007  2009  2011  2013  Web  1G  Smartphone  iPhone  PC  UsEreXpErIeNcE Â
- 8. WehAvETrAdEdPeRfOrMaNcEfOrEvErYtHiNgElSe â˘âŻ Distributing thedata & computation far away personal computing Ă ď web services Ă ď mobile & cloud â˘âŻ Consuming increasingly rich data Text Ă ď Images Ă ď Videos â˘âŻ Moving to highly abstracted & interpreted languages C Ă ď Java Ă ď JavaScript
- 9.
- 10. MoBiLeDeViCeS-5yEaRsBaCkiNCpUSpEeD, 10yEaRsBaCkiNCoNnEcTiOnBaNdWiDtH  Samsung Galaxy S4 My Machine (2003) MyMachine (2010) CPU / MFLOPS 1500 373 4,256 Display / Pixels 2073600 1,920,000 4,096,000 Connection Speed / bps 384000* 300,000 4,000,000 *  Assuming  3G/UMTS  safe  speed,  due  to  low  adopNon  of  4G  networks Â
- 11. 2005  2007  2009  2011  2013  Web  iPhone  HTML5  HtMl5&WeBApPsTo ChAlLeNgE NaTiVeApPsiN SlIcKnEsS Äą11 UsEreXpErIeNcE  UNlizing  HW  accelerated  graphics,  oďŹine  assets,  advanced  gestures  and  high  perf  JS  engines Â
- 12. LeTâsTaRgEtfOrMoBiLeApPPeRfOrMaNcE â˘âŻ 1s appstartup time (ďŹrst page load time) â˘âŻ 1s for any subsequent view/page (reasonable delay) â˘âŻ 100ms UI response time (noticeable delay) â˘âŻ 16ms paints (LCDs will refresh 50-60Hz, the rest is surplus)
- 13. HTML5 App â˘âŻ 1000DOM elements â˘âŻ 1Mb of images and 100 network requests on page load How about these? â˘âŻ 1s ďŹrst page fold Native App â˘âŻ 1000 widgets? â˘âŻ 1Mb of images and 100 network requests on app startup? â˘âŻ 1s application install? WeBeNgInEsaReqUiTe fAsT! LeTâsuSetHesAmEyArDsTiCkwHeNmEaSuRiNg
- 14. IfyOuR eMuLaToRrUnS20tImEs fAsTeR tHaNtHeTaRgEt,wHaTcAn yOueXpEcT aBoUtPeRfOrMaNcE?
- 15.
- 16.
- 17. OnESeCoNdBuDgEt â˘âŻ Turn onradio 300ms! â˘âŻ DNS lookup + 150ms! â˘âŻ SSL handshake + 200ms! â˘âŻ Process & load HTML & other resources + 200ms! â˘âŻ Parse Ă ď Layout Ă ď Paint = 150ms!
- 18. SiMuLaTeSlOwPaGeSpEeDs â˘âŻ Developers tendto have ultra-fast computers & networks and forget the Egde & 3G network â˘âŻ Tip: Network Link Conditioner XCode Plugin & ipfw rules
- 19. AsImPlEsImUlAtIoNShElLScRiPt #!/bin/sh! #! # simulate_3g.sh -Simulate a sluggish 3G network with delays & packet loss! # Usage: simulate_3g.sh 8080 8081! ! # Make sure only root can run our script! if [[ $EUID -ne 0 ]]; then! echo "This script must be run as root" 1>&2! exit 1! fi! ! # Simulate http over 3G, 300kbit/s with 5% packet loss and 200ms delays! # into all ports given as a parameter! ipfw pipe 1 config delay 200 plr 0.1 bw 300kbit/s! for var in "$@"! do! ipfw add 1 pipe 1 dst-port $var! done!
- 20. CoMbInEaNdCoMpReSsyOuRReSoUrCeS â˘âŻ Combine andminify your CSS and JavaScript â˘âŻ Combine small icons into a sprite sheet â˘âŻ Squeeze the last bits from your images: It is much easier to remove 100k from your images than your JavaScript code! â˘âŻ Tip: You should automate this, e.g. using Grunt
- 21. CaChInGtHeAsSeTs â˘âŻ CDNs forcaching assets close to the user â˘âŻ Varnish, Squid, Nginx etc. in front of your app server â˘âŻ Having the CDNs and caches working requires good headers from your app server, too â˘âŻ Tip: Let your Apache/Nginx reverse proxy care for your headers, they usually do it much better than you do Cache-Control: public, max-age=0⨠!Etag: "91580-1380653643000â⨠!Last-Modified: Tue, 01 Oct 2013 18:54:03 GMT!
- 22. ShArDfOrSeVeRaLDoMaInS â˘âŻ Modern browserslimit to 6 connections per host your non- scripted resources (e.g. CSS, images) from several hosts â˘âŻ Severe problem because HTTP 1.1 requires the resources to be sent in the order they were requested â˘âŻ Note: Remember the browser security rules, particularly CORS and Same-origin policy
- 23. If yOuStIlLgOtTiMetOOpTiMiZePaGeLoAdS â˘âŻ Optimizefor the ďŹrst page fold: Critical CSS and JS embeded â˘âŻ Optimize for connection drops & ofďŹine: Application Cache â˘âŻ Batch your API calls â˘âŻ Serve responsive images, prepare for the W3C adaptive images extension !<img alt="The Breakfast Comboâ src="banner.jpegâ⨠! !srcset="banner-HD.jpeg 2x,⨠! !banner-phone.jpeg 100w,⨠! !banner-phone-HD.jpeg 100w 2xâ>!
- 24.
- 25. OlD-ScHoOlOpTiMiZaTiOnSWoNâtHeLpYoU â˘âŻ JavaScript istypically not your problem â˘âŻ CSS selector lengths typically have only a minor impact â˘âŻ Browsers spend ~90% of its computation layouting and painting What you want to track is â˘âŻ The causes of relayout and repainting â˘âŻ What their costs are â˘âŻ Tip: Watch out adding/removing classes & hovering
- 26. âTyPiCaL PaInTLoOpâ FuncNon  call  /  Event  Recalculate  Style  Layout  Paint  Composite  Layers  JavaScript  Engine  (CPU  /  Virtual  Machine)  Render  Tree  &  Layout  Engine  (CPU)  Paint  Engine  (CPU)  Compositor  (GPU) Â
- 27. AlL CsSOpErAtIoNsaReNâtEqUaL â˘âŻ Geometrychanging ops: Layout, repaint, compositing â˘âŻ width, height etc⌠â˘âŻ Paint-only ops: Repaint & compositing only â˘âŻ borders, outlines, box shadow, etc⌠â˘âŻ Composition only (or less): Things that are 100% in GPU â˘âŻ CSS3 Transforms, Opacity
- 28. OpTiMiZiNgLaYoUtS&PaInTs â˘âŻ Avoid DOMreads after geometry changing DOM operations â˘âŻ Avoid a few expensive paint operations (shadows, border radius, ďŹexbox etcâŚ) â˘âŻ Use translateZ(0) hack if you need a HW accelerated element â˘âŻ Use CSS3 transforms for animating, they will not cause reďŹows
- 29.
- 30. TrAdItIoNaLPaGeSDoNâtDo aNyThInGuNtIlyOu TeLl *click* Â *click* Â Tradi&onal Â
- 31. ImMeDiAtEFeEdBaCkbUySYoU tImE OvErAlLpErFoRmAnCemAygEtfAsTeR,tOo *click* Â *click* Â Feedback Â
- 32. PrElOaDiNg&BoOtStRaPpInGToShOwtHeNeXtPaGeFaStEr YoUMaYHuRt YoUrSeLfBaD! *click*  +  *click*  Preloading  Bootstrapping Â
- 33. LaZyLoAd -OpTiMiZiNgfOrtHeFiRsTPaGeFoLd +  +  1st  fold  inlined  Rest  of  the  page  as  separate  resources  +  Lazy  Load Â
- 34.
- 35. ReCaP:GeTtInGtOtHepErFoRmAnCetArGeTs â˘âŻ Set theperformance goals, prepare for tradeoffs â˘âŻ Track the goals from the beginning â˘âŻ Donât guess; measure â˘âŻ Simulate the target performance as part of your daily work â˘âŻ Keep your code simple, donât trade it for performance â˘âŻ Perfect is the enemy of the good
- 36.
- 37. HtMl5 eXpErTiSeaTyOuRsErViCe  LaUrISvAn ThAnKyOu! SoftwareArchitect, SC5 Online Ltd https://github.com/laurisvan https://twitter.com/laurisvan