Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Your customers care about how fast your application works, you should too.... At Heroku we see millions of apps deploy and we know what it takes to get serious performance out of your code and Rails. In this talk we'll cover backend tips and frontend tricks that will help your Rails app go faster than ever before. Help us caption & translate this video! http://amara.org/v/FGaI/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Forget Scaling: Focus on Performance" features Terence Lee at Rails Conf 2013, discussing the importance of enhancing application performance over scaling at the outset. The main theme revolves around optimizing both backend and frontend efficiency for Rails applications to ensure faster response times and better throughput. ### Key Points Discussed: - **Performance versus Scaling**: The initial focus should be on optimizing performance for a single app, thus easing the future scaling process. - **Speed vs Throughput**: Speed refers to the response time for a single request, while throughput indicates the number of requests or data processed over a period. Both are interlinked. - **Web Servers**: Lee differentiates between single request servers and concurrent request servers. He recommends using concurrent servers (like Puma and Unicorn) for better throughput, explaining the threading and process concurrency in Ruby applications. - **Optimal Server Configuration**: He advises testing the number of Unicorn workers on Heroku to balance performance and memory usage efficiently, using monitoring tools for insights. - **Database Performance**: Tips for optimizing backend performance include using Auto Explain in Rails, adding indexes to slow queries, and utilizing PostgreSQL’s `pg_stat_statements` for monitoring query performances. - **Performance Monitoring**: He stresses the necessity of using tools like New Relic and Librato for monitoring application performance, likening performance issues to visibility challenges. - **Frontend Optimization**: Suggestions include minifying assets, using Content Delivery Networks (CDNs) for faster asset delivery, and configuring Rails for asset fingerprinting to manage cache effectively. - **Scaling Strategy**: Discusses approaches to scaling up (vertical scaling) versus scaling out (horizontal scaling), recommending allocating read workloads to database followers to maintain application efficacy under load. - **Final Takeaways**: Conclusively, the talk emphasizes the architecture's role in managing scaling concerns, encouraging concurrent server use, ensuring database efficiency, and utilizing CDNs for frontend speed. Lee highlights the performance bar in the expo hall for hands-on help with best practices and troubleshooting.
Suggest modifications
Cancel
