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 benchmarks shared by the bun team (see above links) look like there is a considerable amount of time to be saved, in case the connection is used often enough/the hosts have enough distance in between.
I wonder whether PHP could also provide such kind of startup-time pre-connect things so we don't need to re-establish connections at every request.
DNS resolution or TLS connection handshakes could already be completed before the PHP script beeing run even knows it will need it later
The text was updated successfully, but these errors were encountered:
This is related to cURL? CURLOPT_FORBID_REUSE and CURLOPT_FRESH_CONNECT with false? or CURLOPT_RESOLVE for skip DNS resolution? Nice idea to have pre-connect at level startup time (FPM?)
Description
browser have a html tag to pre-connect to hosts, also bun (a competitor to nodejs) added support for pre-connecting to hosts, like databases, http-hosts etc.
the benchmarks shared by the bun team (see above links) look like there is a considerable amount of time to be saved, in case the connection is used often enough/the hosts have enough distance in between.
I wonder whether PHP could also provide such kind of startup-time pre-connect things so we don't need to re-establish connections at every request.
DNS resolution or TLS connection handshakes could already be completed before the PHP script beeing run even knows it will need it later
The text was updated successfully, but these errors were encountered: