View: 
Categories
- Active Record
- Active Resource
- Active Support
- Administration
- Ajax
- APIs
- Authentication
- Authorization
- Background Jobs
- Caching
- Code Walkthrough
- Controllers
- Debugging
- Deployment
- eCommerce
- Forms
- Mailing
- Models
- Performance
- Plugins
- Production
- Rack
- Rails 2.0
- Rails 2.1
- Rails 2.2
- Rails 2.3
- Rails 3.0
- Rails 3.1
- Rails 3.2
- Rails 4.0
- Refactoring
- Routing
- Search
- Security
- Testing
- Tools
- Views
Applied Filters:
Performance x
Rake in Background
In need of a background process? You may be able to accomplish this with a simple Rake task. See how in this episode.
(10 minutes)
Request Profiling
You can use profiling to determine where the performance bottlenecks are in specific Rails actions. Watch this episode for details.
(10 minutes)
Analyzing the Production Log
In order to improve performance of your Rails application you need to find the bottlenecks. A great starting point is your production log. In this episode you will see how to use RAWK to analyze your log file and determine which controller actions take up the most processing time.
(5 minutes)
Action Caching
Action caching behaves much like page caching except it processes the controller filters. You can also make it conditional as seen in this episode.
(7 minutes)
Fragment Caching
Sometimes you only want to cache a section of a page instead of the entire page. Fragment caching is the answer as shown in this episode.
(6 minutes)
Page Caching
Page caching is an efficient way to cache stateless content. In this episode I will show you how to cache the dynamic javascript we created last week.
(6 minutes)
Counter Cache Column
If you need to display the record count for a has_many association, you can improve performance by caching that number in a column.
(7 minutes)
Eager Loading
One way to improve performance is to cut down on the number of SQL queries. You can do this through eager loading. Learn all about it in this episode!
(4 minutes)
Caching with Instance Variables
Learn a quick way to improve performance. Just store the end result of an expensive command in an instance variable!
(2 minutes)