>
> My thinking is that perhaps every time a page is rendered, a mongrel has
> to instantiate this controller and that marshalling this into RAM is
> very time-consuming.  Or does a controller get loaded into RAM at server
> startup and then the effect is not all that substantial for each page?
> Any ideas on this?
>

I'm not familiar with Mongrel-based hosting, but in Passenger classes are
cached in memory when loaded and instantiated from that.  The cost of
instantiating a new object shouldn't be that onerous (even if you have a
zillion methods) as it's only a pointer to the class at that point and an
instance data created during instantiation.

I am familiar with Ruby profiling and we are looking into that too.
>

Personally I'd recommend testing it on a Mac and using DTrace to get a
really good insight in to where it's spending it's time.  I've had a lot of
success with that in the past.

Cheers,


Andy

-- 
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 rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to