improving the performance of Rails web Applications
by John McCaffrey on Jul 21, 2010
- 1,846 views
This presentation is the first in a series on Improving Rails application performance. This session covers the basic motivations and goals for improving performance, the best way to approach a performa...
This presentation is the first in a series on Improving Rails application performance. This session covers the basic motivations and goals for improving performance, the best way to approach a performance assessment, and a review of the tools and techniques that will yield the best results. Tools covered include: Firebug, yslow, page speed, speed tracer, dom monster, request log analyzer, oink, rack bug, new relic rpm, rails metrics, showslow.org, msfast, webpagetest.org and gtmetrix.org.
The upcoming sessions will focus on:
Improving sql queries, and active record use
Improving general rails/ruby code
Improving the front-end
And a final presentation will cover how to be a more efficient and effective developer!
This series will be compressed into a best of session for the 2010 http://windycityRails.org conference
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 5
- Downloads
- 31
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,748
- Total Views
- 1,846
How does performance matter for your app?
http://googlewebmastercentral.blogspot.com/2010/04/using-site-speed-in-web-search-ranking.html
http://www.websiteoptimization.com/speed/tweak/page-speed-search-rankings/
8000 requests per second
parallel downloads alone lead to a 0.5% increase in topline revenue
info and graphs from http://www.phpied.com/the-performance-business-pitch/
it has to be worth it from a business point of view
scalability is how many jobs you can handle
http://tools.pingdom.com/
http://www.site-perf.com/
primed cache
score
time to load
rules
requests, parsing, blocking, rendering, reflow, ajax
Chrome tool
http://code.google.com/webtoolkit/speedtracer/get-started.html
check your site with the IE tools to see if the numbers match
Its a quick way to get you thinking about what you should be looking into, but don't make any changes yet.
Document your findings
http://www.site-perf.com/
against multiple environments
write down what numbers you got on which day (maybe iTunes free music day really kills the bandwidth in your office)
add some load
http://www.xenoclast.org/autobench/
httperf
you can store just your info locally, if you aren’t cool with sending your data to another site
you want to customize