Help with modrails and Apache2

I am using modrails and Apache2. The first time I use my app it goes
very slow but later it goes very fast. If I don’t use the app during 20
min, again the first clic goes very slow and later it goes fast. What’s
the problem?

You might go over to the mod_rails forum and try posting there.

Also, I just now saw this post after replying to your earlier one. My
response there is useless if you are using mod_rails.


P.S. I’m still working on switching to mod_rails, otherwise I’d try
fiddling and see what I could find out. I’m very interested in this,
though, as I’m considering migrating to mod_rails for all my hosted
rails apps. So if you do discover a solution, please post it!

On Apr 24, 5:08 am, John S. [email protected]

Where IS the mod_rails forum??

This is actually to be expected to an extent with the default
configuration. Basically there is a connection pool and if there are no
hits for a given period of time than the connections are destroyed. Once
a request occurs, the connections are brought back up online. This can
take a second or two. That might not be 100% technically correct but
thats the idea.

However, this can be tweaked by playing with two variables in the apache

  • RailsPoolIdleTime
  • RailsMaxPoolSize

By extending the idle time and lowering pool size, you can simulate a
mongrel type situation with processes that run for a long time.

Mod_rails was originally called Phusion.



On 24 avr, 16:10, Danimal [email protected] wrote:

You might go over to the mod_rails forum and try posting there.

So there ise a mod_rails forum! Where it is please?

– Maurice

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs