On Thu, 27 Jun 2024, Dmitry Karpov via curl-library wrote:
In memory constrained and slow systems, like embedded devices, saving a
fraction of a second on resource releases (or several hundred milliseconds
on slow devices) may be a very important benefit, which will overweigh
potential delays in port reuses.
That's why I suggested to have an option which would sacrifice faster port
reuse but will allow to get faster connection resource release.
This fix also helps for such resource constrained situations. libcurl has
always, since before Stefan's fixes, been sloppy at closing (TLS) connections
and in situation where you end up with a large volume of closed connections
you could find yourself unable to start new connections because of the wait
states from the previous ones still lingering.
This fix should make us get faster connection resource release than before,
because it helps shut down the TCP correctly so the TCP stack can release the
resources quicker.
But we are open to adding options to allow tweaking and customizing of the
options, sizes and timeouts involved if people actually run into situations
where such are needed.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
