Ruby on Rails

On Sunday, March 31, 2013 10:57:24 PM UTC+1, rocdaddy wrote:
> Hey folks:
>
> In a rails app I'm building, the home page will have two forms:  one to sign-up for an account, another one to sign-in to an existing account.
>
> Now, if I were to use object form helpers to build these forms, the controller for the homepage would need to create instances of the relevant models each time someone visits the homepage.
>
> This concerns me a bit, because a visitor to the home page may or may not end up using either the sign-up or sign-in forms.  For instance, they may instead click a link that gives a "tour" of the app.  If they do so, will the instance variables created by the controller in anticipation of the POTENTIAL use of the forms be garbage-collected?
>

They would be, along with many hundreds or thousands of other objects created for the request: strings, request related objects (parsed headers, cookies etc). A few model objects are neither here nor there in the grand of scheme. For me this falls into the category of premature optimization. If you really do end up serving millions of daily hits on your homepage then you'll get a far bigger win from caching than from skimping on a few instance variables

Fred

> I'm just thinking about efficiency here -- don't want to have a bunch of extra instance variables taking up space in the runtime memory just for the sake of the (slight) convenience of using model object forms helpers rather than plain-vanilla form handlers.
>
> Thanks!

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/iz34APKbU30J.
For more options, visit https://groups.google.com/groups/opt_out.