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

run_pipeline: Bound concurrent option to a reasonable number #65

Closed
chfoo opened this issue Aug 29, 2014 · 0 comments
Closed

run_pipeline: Bound concurrent option to a reasonable number #65

chfoo opened this issue Aug 29, 2014 · 0 comments
Assignees

Comments

@chfoo
Copy link
Member

chfoo commented Aug 29, 2014

Limit the --concurrent N maximum to a reasonable number such as 10 to avoid users running hundreds of threads at a time. This reduces the problem where a user claims thousands of items but does not return most of the claims. A warning message could be used if the user runs more than 6. (No need to test the C10K ability of Tornado 😄)

@chfoo chfoo self-assigned this Sep 8, 2014
@chfoo chfoo closed this as completed in a53cfe3 Sep 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant