You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intent of v4.0.0 is to help mitigate bottlenecks when using Wreck and agent pooling. By default, on node v0.10, maxSockets is set to 5. This can cause slowness if there are a lot of requests that need to be made as only 5 sockets will get to be used. In node v0.11 this default value is changed to Infinity. Wreck v4.0.0 follows this lead and now defaults the maxSockets to Infinity.
Breaking Change
To avoid overwriting the maxSockets value in the node http and httpsglobalAgentWreck creates new agents. These agents are exported under the agents object in Wreck. If you need to change the maxSockets value from Infinity then you will need to change either Wreck.agents.http.maxSockets or Wreck.agents.https.maxSockets.
In other words, changing the globalAgent no longer has an impact on the default agent used by Wreck.
Enhancement
Agent pooling can now be disabled by passing false for the value of agent when calling a Wreck request function.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
The intent of v4.0.0 is to help mitigate bottlenecks when using Wreck and agent pooling. By default, on node v0.10,
maxSockets
is set to 5. This can cause slowness if there are a lot of requests that need to be made as only 5 sockets will get to be used. In node v0.11 this default value is changed toInfinity
. Wreck v4.0.0 follows this lead and now defaults themaxSockets
toInfinity
.Breaking Change
To avoid overwriting the
maxSockets
value in the nodehttp
andhttps
globalAgent
Wreck creates new agents. These agents are exported under theagents
object in Wreck. If you need to change themaxSockets
value fromInfinity
then you will need to change eitherWreck.agents.http.maxSockets
orWreck.agents.https.maxSockets
.In other words, changing the
globalAgent
no longer has an impact on the default agent used by Wreck.Enhancement
Agent pooling can now be disabled by passing
false
for the value ofagent
when calling a Wreck request function.The text was updated successfully, but these errors were encountered: