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

Improved performance by tweaking agent.maxSockets #53

Closed
jimlears opened this issue Dec 15, 2011 · 4 comments
Closed

Improved performance by tweaking agent.maxSockets #53

jimlears opened this issue Dec 15, 2011 · 4 comments

Comments

@jimlears
Copy link

This is more of a question than an issue. Will Knox be able to handle massive concurrency putting files on S3 w/o tweaking agent.maxSockets to be something greater than 5? If so, any suggestions/best practices for setting this number and/or other options for getting better perf. under heavy load?

@masterkain
Copy link

Is the project still alive?

@tj
Copy link
Contributor

tj commented Mar 23, 2012

we could probably use some maintainers, it's hard for me to get around to everything. We're not using S3 a whole lot anymore right now but I don't doubt that we will in the near future

@traviscooper
Copy link

@visionmedia what are you using in place of s3?

@domenic
Copy link
Contributor

domenic commented Jul 16, 2012

This is overly vague to be a bug report. @jimlears if there is anything you think Knox could do, or if you can explain the problem you're having better, I'd love to help. Otherwise, closing for now.

@domenic domenic closed this as completed Jul 16, 2012
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

5 participants