Using Node.js to Improve the Performance of Mobile Apps and Mobile Web
•
0 recomendaciones•1,038 vistas
Video and slides synchronized, mp3 and slide download available at http://bit.ly/11aNbSq. Tom Hughes-Croucher discusses increasing the performance of web applications and websites by using Node.js’ event-driven approach. Filmed at qconsf.com. Tom Hughes-Croucher has worked in the Web industry for over a decade. He is the founder and principal at Jetpacks for Dinosaurs, a consultancy specializing in high-scale and high performance Internet applications for clients such as Walmart, Comcast and MySpace. Tom has co-authored W3C Standards and O'Reilly's "Up and Running with Node.js".
Recomendados
Recomendados
Más contenido relacionado
Más de C4Media
Más de C4Media (20)
Último
Último (20)
Using Node.js to Improve the Performance of Mobile Apps and Mobile Web
- 1. Using Node.js to improve the performance of Mobile apps and Mobile web Tom Hughes-Croucher @sh1mmer
- 2. Watch the video with slide synchronization on InfoQ.com! http://www.infoq.com/presentations /Nodejs-Performance-Web InfoQ.com: News & Community Site • 750,000 unique visitors/month • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • News 15-20 / week • Articles 3-4 / week • Presentations (videos) 12-15 / week • Interviews 2-3 / week • Books 1 / month
- 3. Presented at QCon San Francisco www.qconsf.com Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide
- 4. Scalable Server-Side Code with JavaScript Who is Tom? • Wrote W3C Standards • • 10+ years in the web industry Worked on projects for: Tesco, NASA, Walmart, MySpace, etc Node Up and Running • ~5 years at Yahoo! including .com Tom Hughes-Croucher • Node team at Joyent @sh1mmer
- 5. This is a talk about why cell phones suck. @sh1mmer
- 6. @sh1mmer
- 7. Radio waves suck (at least compared to fibre or copper) @sh1mmer
- 10. @sh1mmer
- 11. @sh1mmer
- 12. @sh1mmer
- 13. @sh1mmer
- 14. @sh1mmer
- 15. Desktop Mobile http://www.webperformancetoday.com/2012/04/02/mobile-versus-desktop-latency/ @sh1mmer
- 16. Ookla/speedtest.net via http://www.slideshare.net/patrickmeenan/velocity-2012-taming-the-mobile-beast/22 @sh1mmer
- 17. Effect of latency on servers @sh1mmer
- 19. nginx haproxy web services frontends ATS / data varnish @sh1mmer
- 20. var client = net.connect(80, domain, function() { client.write("GET / HTTP/1.1rn"); t1 = (new Date()).getTime(); }); client.on('end', function() { t2 = (new Date()).getTime(); output.write(domain + ' ' + ((t2-t1)/1000) + 'sn'); }); @sh1mmer
- 21. Sample of Alexa 5000 macupdate.com 442.3 uzai.com 403.658 wired.jp 238.848 facilisimo.com 205.159 mycokerewards.com 202.757 rbc.cn 192.354 moviesmobile.net 183.157 stop55.com 145.927 dir.bg 137.982 carrefour.fr 112.789 sifyitest.com 111.171 @sh1mmer
- 23. Client → Server Server → DB Computation Computation @sh1mmer
- 24. Not an event frontend @sh1mmer
- 25. @sh1mmer
- 26. Server @sh1mmer
- 27. Request @sh1mmer
- 28. @sh1mmer
- 31. @sh1mmer
- 32. Shared Work Resources @sh1mmer
- 34. var x = "I am a string" ~1ns Running 1 instruction 2ns Data from l1 cpu cache 5ns Data from l2 cpu cache 80ns Data from ram @sh1mmer
- 35. @sh1mmer
- 37. @sh1mmer
- 38. 100 Blue Whales Cat @sh1mmer
- 39. "They went from running 15 servers with 15 instances (virtual servers) on each physical machine, to just four instances that can handle double the traffic." http://venturebeat.com/2011/08/16/linkedin-node/ @sh1mmer
- 40. Not just simple applications @sh1mmer
- 41. @sh1mmer
- 42. @sh1mmer
- 43. First page load vs. Client MVC @sh1mmer
- 45. @sh1mmer
- 47. Bandwidth Latency Device capability @sh1mmer
- 48. Barfing data at 3G @sh1mmer
- 49. @sh1mmer
- 50. @sh1mmer
- 52. @sh1mmer
- 53. Node.js allows you to tune rendering between client and server based on the network. @sh1mmer
- 54. HTML JSON More bandwidth Less bandwidth Less client processing More client processing Battery friendly Cheaper for you bandwidth/server Cheaper for them bandwidth @sh1mmer
- 56. Challenges • JSON - fast object / slow render • HTML - fast render / slow objects • If we use HTML where do we manage our model? • If we use JSON does rendering matter? @sh1mmer
- 57. Identifying use cases • "Client-side apps" - read/write data on client • "Render-only apps" - mostly read data on client @sh1mmer
- 58. Summary • Node.js allows you to: • Manage resources with unreliable mobile data connections • Choose where to apply rendering • Pick the right rendering solution for the right scenario @sh1mmer