[tog] Performance problems under passenger

[Jacobo García]

Hi,

First of all, congrats for this fantastic piece of software.

Now, the not so good part:

We are experincing slowness using tog in conjunction with passenger.
Specially on first run. I already know that passenger is slow on first
run, but it takes a lot (almost 25 seconds to start).

Anyone else having this problems? Any help will be appreciated.


Jacobo García López de Araujo
blog: http://robotplaysguitar.com
http://workingwithrails.com/person/13395-jacobo-garc-a

--
You received this message because you are subscribed to the Google Groups "tog_users" group.
To post to this group, send email to tog_...@googlegroups.com.
To unsubscribe from this group, send email to tog_users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tog_users?hl=en.

[Alberto Molpeceres]

Hi,

Not sure if this is the case, 25 seconds sounds pretty long, but tog
is slow on startup, that is a fact. This is mainly caused by desert
and it's merging of classes overwritten in plugins and your app. This
is the price for it's simplicity on extending and overwriting tog's
plugins and it's modularity.

I'm not sure how could we improve this, or in fact, if it's a real
necessity since (at least in my case) deploy is something done not
very often. But we are open to ideas on this issue.

al.

[Jacobo García]

Hi,

The problem goes when application becomes iddle, not only on
deployments. I've solved the problem 'curling' the home of the
website before passenger times out.

Regards.

Jacobo García López de Araujo
blog: http://robotplaysguitar.com
http://workingwithrails.com/person/13395-jacobo-garc-a

[Alberto Molpeceres]

On Thu, Apr 22, 2010 at 10:56 AM, Jacobo García <jacobo...@gmail.com> wrote:
> Hi,
>

> The problem goes when application becomes iddle, not only on
> deployments. I've solved  the problem 'curling' the home of the
> website before passenger times out.
>

What a hack XD.

Well, it's just apache is reloading the rails app, so it makes sense
to me. Not sure if you could config passenger to change this behavior
if the application is critical.

I'll check some of our apps and check how long it takes to load the
app. Could you give me the URL of your app to see how complex it is to
compare with one of ours?

al.

[Dan Blue]

Passenger cleans up idle Rails instances after a period of idling. You can trade off idling for growing memory profile by increasing the idle time in your Passenger configuration (PassengerPoolIdleTime, RailsFrameworkSpawnerIdleTime or RailsAppSpawnerIdleTime) or setting them to 0 so that they never timeout. See http://modrails.com//documentation/Users%20guide.html#_configuring_passenger for more details.

And Google is your friend.