Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
because
gem 'gem_name' # Rails 3.0
or
config.gem 'gem_name' # Rails 2.x
will load the gem no matter what the controller is… will a
require 'gem_name'
in the controller source code actually make the Rails server run faster because not every controller will load that gem?
The short answer is: no.
Stick with keeping your code sane and maintainable by grouping your required gems in your
Gemfile/environment.rb.I would need to see some well crafted performance data before I’d believe that this would ever make a noticeable difference in a production environment. There are so many other places to optimize first.