After a long idle-time the server take very long to deliver the first page. about passenger HOT 11 CLOSED

From honglilai on April 22, 2008 10:14:53

RailsMinPoolSize wouldn't really help, because if Apache serves multiple Rails
applications, then application A's instances cannot be reused for application B.

However, the FrameworkSpawner server can reduce startup time because it preloads the
entire Rails framework (which usually accounts for at least half of the startup
time). Currently the idle timeout for this is a constant and is not configurable. In
the future, a configuration option can be added.

If you want to change the timeout, please edit lib/passenger/spawn_manager.rb,
constant FRAMEWORK_SPAWNER_MAX_IDLE_TIME.

Labels: -Type-Defect Type-Enhancement

from passenger.

From brejoc on April 25, 2008 02:26:34

Thank you for you quick reply, honglilai!

In my case (currently only one simultaniously used version of rails) it worked without any downside.

from passenger.

From cpisto on May 22, 2008 10:47:39

I definitely agree that "RailsMinPoolSize" (per vhost) would be the most intuitive,
and arguably correct, solution

from passenger.

From google%[email protected] on October 04, 2008 07:31:25

I think honglilai is correct, a better solution would be PassengerMinInstancesPerApp

from passenger.

From frankske on December 08, 2008 03:48:16

I agree on the PassengerMinInstancesPerApp. You'd want at least one instance running per app!

from passenger.

From drothlis on January 24, 2009 06:18:34

It would be really useful to have a directive similar to PassengerMaxInstancesPerApp,
but setable individually for each app/virtualhost.

(I run a critical app along with several low-traffic, non-critical apps on the same
server; I would like each of the non-critical apps to have at most one instance
running, leaving several instances available for the critical app.)

from passenger.

From will.bryant on February 27, 2009 17:30:40

I'd really like a PassengerMinInstancesPerApp. I get about 5s startups, which is too poor for me.

To the original commenter though, instances should not take a minute to start under any circumstances. It
shouldn't take noticeably longer than it takes to run up a script/server, so I'd suggest you try that. If the server
is badly overloaded, you need a better server; if the server isn't loaded but startup seems to freeze up, fire up a
debugger and see what it's doing - it may be freezing up trying to get something off the network before timing
out, for example.

from passenger.

From dolzenko on September 17, 2009 23:26:44

Ow, just wasted some time looking through the code and not reading docs throughly before
that, but anyway it seems to be worth adding to the first comment that the configuration
options were added for this: http://www.modrails.com/documentation/Users%20guide %20Apache.html#_railsframeworkspawneridletime_lt_integer_gt http://www.modrails.com/documentation/Users%20guide %20Apache.html#_railsappspawneridletime_lt_integer_gt

from passenger.

From dolzenko on September 17, 2009 23:27:48

Screwed the links, these are to the following sections from the docs:

5.14.5. RailsFrameworkSpawnerIdleTime
5.14.6. RailsAppSpawnerIdleTime

from passenger.

From honglilai on November 17, 2009 11:05:25

PassengerMinInstances has been implemented in a not-yet-published refactoring branch.
Will push when the time is right.

Status: Fixed
Labels: Milestone-3.0.0

from passenger.

From steffen.hiller on November 17, 2009 13:38:05

Interesting!

from passenger.