Download to read offline
![N+1 Query detected
Experience => [:interest]
Add to your finder: :include => [:interest]](https://image.slidesharecdn.com/rails-performance-130114115009-phpapp02/85/Performance-When-What-and-How-32-320.jpg)
Uploaded byAstrails
Performance - When, What and How
Vitaly Kushner discusses performance optimization in Rails applications, emphasizing the importance of speed, throughput, and scalability as user bases grow. He provides tools and techniques for measurement and improvement, such as Yahoo YSlow, Google PageSpeed, and various code optimizations, while cautioning against premature optimizations due to limited time and budget. The presentation highlights the need for a scalability plan and encourages celebrating growth milestones, even if performance issues arise.
More Related Content
Similar to Performance - When, What and How
Performance - When, What and How
- 1. Rails Performance When, What and How Vitaly Kushner @vkushner
- 2. Vitaly Kushner programming sincemiddle 80s professionally since early 90s Rails since 2005 founded Astrails in 2008
- 3.
- 4.
- 5.
- 6.
- 7. performance • raw speed •throughput • scalability • end-user
- 8. No time to diveinto details
- 9. When to optimize? and when not to.
- 10. what to dowith 1M users
- 11.
- 12.
- 13. NOT because of performanceproblems
- 14.
- 15.
- 16. have scalability problem?
- 17. GREAT! because it meansyou grow fast
- 18.
- 19. Scalability Plan • understandthe limits • know your next step
- 20. performance doesit matter?
- 21. YES! performance is veryimportant
- 22. Is 1% alot? yes, if you are Google.
- 23. Why not tooptimize anyway?
- 24. time and budget usually limited
- 25. Measure You can notimprove what you do not measure.
- 26. Tools • Yahoo Yslow http://developer.yahoo.com/yslow/ • Google PageSpeed https://developers.google.com/speed/pagespeed • NewRelic - http://newrelic.com • httperf & ab • Blitz.io
- 27. limit number ofrecords from the database
- 28.
- 29. Instantiation Breakdown: Total:14 | User: 4 | Experience: 3 | Location: 3 | Interest: 3 | Admin: 1
- 30. limit number ofqueries prevent 1+N queries problem
- 31.
- 32. N+1 Query detected Experience=> [:interest] Add to your finder: :include => [:interest]
- 33. define indexes can be done later
- 34.
- 35. limit number ofhttp requests consolidate assets assets pipeline makes it easy
- 36. css at thetop js at the bottom improves perceived page speed
- 37. low level hacks •replace :include with :join • explicit :select
- 38.
- 39. Maintainability usually betterthen speed
- 40. low hanging fruits •compress and http cache assets • CDN libraries • image sprites • bundle images into CSS • CDN for all static assets
- 41.
- 42. real performance problem?
- 43.
- 44. Thank you! Slides andvideo will be published at http://astrails.com/blog Vitaly Kushner @vkushner