Skip to content
This repository has been archived by the owner on Nov 9, 2023. It is now read-only.

Smaller pool by default #14

Closed
rauchg opened this issue Jan 17, 2018 · 1 comment
Closed

Smaller pool by default #14

rauchg opened this issue Jan 17, 2018 · 1 comment
Labels
enhancement

Comments

@rauchg
Copy link
Member

rauchg commented Jan 17, 2018

Right now it's 200, which is good for many use cases, but overkill for others. As an example, if you write a little utility that abstracts over fetch, and someone uses it as a module, they get a 200 socket pool by default.

A more reasonable default would be 50
@MunifTanjim MunifTanjim mentioned this issue Oct 14, 2018
Closed
OlliV referenced this issue in turist-cloud/fetch Nov 12, 2019
@OlliV
Set maxSockets from 200 to 50
263669f 
Closes #14 Smaller pool by default
@OlliV OlliV mentioned this issue Nov 12, 2019
Closed
@Ethan-Arrowood
Copy link
Collaborator

Thank you for the report. We are archiving this project; you can read more details here: #83

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set maxSockets from 200 to 50 turist-cloud/fetch
2 participants
@rauchg @Ethan-Arrowood