Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to understand max_overflow #100

Open
wminghao opened this issue Jul 14, 2017 · 4 comments
Open

Trying to understand max_overflow #100

wminghao opened this issue Jul 14, 2017 · 4 comments

Comments

@wminghao
Copy link

wminghao commented Jul 14, 2017

Hi,

I am trying to whether poolboy can dynamically increase the pool size until it reaches the size.

Allocating resources in the beginning of the world seems to be wasteful.

Regards,
Thanks

@atlas-comstock
Copy link

atlas-comstock commented Mar 30, 2018

@wminghao
poolboy will allocating child at the beginning.

If you don't want this , you can set size to 1 and max_overflow to the size you want.
When the size(1) of workers are all checked out, then poolboy can dynamically new works for you. Except that in this situation poolboy have to start_child for you, which may cost a little time, othes are all the same.

@atlas-comstock
Copy link

atlas-comstock commented Mar 30, 2018

@devinus
Am I right? I figured out this by reading code.

@zugolosian
Copy link

That sounds right ^ It'll only start overflow workers when all the original workers are checked out

@Vagabond
Copy link
Collaborator

Vagabond commented Jul 5, 2018

Yes, overflow children are started on-demand (and destroyed on being checked back in).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants