Rails website start up time

Rails
#1

My application is starting/loading very late when hit my website url
in the browser.
Can anybody give some tips to optimize it please.

#2

On Sat, Oct 1, 2011 at 12:22 PM, venkata reddy
[email protected]wrote:

My application is starting/loading very late when hit my website url
in the browser.
Can anybody give some tips to optimize it please.

1.Optimize your sql queries
2. Tune the passenger, options like HighPerformance on
3. Remove the unwanted modules on Apache as per your exact need

#3

On Sat, Oct 1, 2011 at 8:52 AM, venkata reddy
[email protected]wrote:

My application is starting/loading very late when hit my website url
in the browser.
Can anybody give some tips to optimize it please.

Is this on the “production” and/or the “development” server?

Is it the case that the very first click after a new deployment on
production is slow (starting/loading the application) and the next
clicks
are much faster (once they are all loaded in production mode)?

Which web server module and which ruby version are you using?

Peter

#4

Don’t Right Ruby code in .erb file. If you want then you can write
controller.rb file then your application load easy

by
bdeveloper01

#5

I’m actually curious about this.

I thought that all erb code and its rails variables are all prepared
before
the actual erb file gets loaded and its not rendered on the fly?

David

#6
Have a look at http://railslab.newrelic.com/scaling-rails

El 01/10/2011 9:16, loganathan sellappa escribió:
On Sat, Oct 1, 2011 at 12:22 PM, venkata reddy <[email protected]> wrote:
My application is starting/loading very late when hit my website url
in the browser.
Can anybody give some tips to optimize it please.
   1.Optimize your sql queries
   2. Tune the passenger, options like HighPerformance on
   3. Remove the unwanted modules on Apache as per your exact need 

--
You received this message because you are subscribed to the Google G. "Ruby on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.


--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

--
Miquel C. Escarré

–

You received this message because you are subscribed to the Google
Groups “Ruby on Rails: Talk” group.

To post to this group, send email to
[email protected]

To unsubscribe from this group, send email to
[email protected]

For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.

#7

On Sat, Oct 1, 2011 at 22:38, David C. [email protected] wrote:

I thought that all erb code and its rails variables are all prepared before
the actual erb file gets loaded and its not rendered on the fly?

That’s the goal to strive for, but if it’s all not rendered on the
fly, that means it’s static, in which case why bother using ERb? :slight_smile:
Having Ruby code in your ERb files is a necessary evil. The trick is
to do as much as possible of the complicated logic in the other parts.
The things that respond at a very high level to the current “command”
(like “tell the model to make a new one” or “tell the model to tag
this post with this comment”) are generally in the controller, while
the logic behind that (the actual creation or tagging) is usually in
the model.

-Dave

–
LOOKING FOR WORK, preferably Ruby on Rails, in NoVa/DC; see main web
site.
Main Web S.: davearonson.com
Programming Blog: codosaur.us
Excellence Blog: dare2xl.com