HTTP performance best practice about ghostunnel HOT 3 CLOSED

The most computationally expensive part of TLS is the handshake. To reduce the overhead from handshakes I would (1) use persistent long-lived connections where possible and (2) make sure to use an ECDSA (on P-256) certificate instead of an RSA certificate. This should be faster then RSA, as P-256 is implemented in assembly (on amd64 and s390x at least) whereas RSA is not. Also, make sure your CPU supports AES-NI instructions.

Additionally, you can leverage the SO_REUSEPORT feature (on UNIX) to run multiple instances of Ghostunnel in parallel on the same host/port and with the same target. The kernel will then load-balance new connections evenly between each Ghostunnel process which can help scale to the CPU resources in your system.

from ghostunnel.

To add to that, right now Ghostunnel always maps client connections and backend connections 1:1, and there's no way to keep those open or re-use if the client closes them. Since Ghostunnel is protocol-agnostic it's not (in general) safe to keep the connections open. So if you're specifically forwarding HTTP you might be better off with a protocol-specific proxy like haproxy that can do things like cache, introspect, etc. the HTTP requests.

from ghostunnel.

Ah and the log is normal/expected. The use of closed network connection just means the client and/or server closed the connection, Ghostunnel noticed it's closed, and then terminated the other end of the connection.

from ghostunnel.