min-instances and max-pool-size

[fschwahn]

Hi,
first of all, I'm slightly confused why the Procfile in this example differs slightly from your new deployment walkthrough - is there a reason for this?

Secondly, in your Optimization Guide you write that process spawning should be minimized by setting max-pool-size and min-instances to the same value. Isn't heroku the perfect place to follow this advice, because there will always only be 1 app on a server? If it is indeed like that, maybe it makes sense to either adjust this example repo, or add this advice to the README.

What do you think?

All the best,
Fabian

[FooBarWidget]

first of all, I'm slightly confused why the Procfile in this example differs slightly from your new deployment walkthrough - is there a reason for this?

I do not understand what you mean. The Procfile in the README is the exact same as the one in the deployment walkthrough. They both tell you to set web: bundle exec passenger start -p $PORT --max-pool-size 3.

Secondly, in your Optimization Guide you write that process spawning should be minimized by setting max-pool-size and min-instances to the same value. Isn't heroku the perfect place to follow this advice, because there will always only be 1 app on a server? If it is indeed like that, maybe it makes sense to either adjust this example repo, or add this advice to the README.

Yes, you have a point there. On the other hand, I do not want to bother people too much with configuration options when they are just starting to understand Passenger.

[fschwahn]

Ah, I'm sorry about the first point, you are rights that in the README it is identical - however the file in the repository (https://github.com/phusion/passenger-ruby-heroku-demo/blob/master/Procfile) is slightly different. That's what I looked at.

[FooBarWidget]

I see. I will have a look at that.