async-http-client

0 Fork 0

mirror of https://github.com/swift-server/async-http-client.git synced 2026-06-02 07:37:34 +00:00

Files

T

Johannes Weiss e2d03ffb32 cache NIOSSLContext (saves 27k allocs per conn) (#362 )

Motivation:

At the moment, AHC assumes that creating a `NIOSSLContext` is both cheap
and doesn't block.

Neither of these two assumptions are true.

To create a `NIOSSLContext`, BoringSSL will have to read a lot of
certificates in the trust store (on disk) which require a lot of ASN1
parsing and much much more.

On my Ubuntu test machine, creating one `NIOSSLContext` is about 27,000
allocations!!! To make it worse, AHC allocates a fresh `NIOSSLContext`
for _every single connection_, whether HTTP or HTTPS. Yes, correct.

Modification:

- Cache NIOSSLContexts per TLSConfiguration in a LRU cache
- Don't get an NIOSSLContext for HTTP (plain text) connections

Result:

New connections should be _much_ faster in general assuming that you're
not using a different TLSConfiguration for every connection.

2021-05-13 12:16:52 +01:00

NIOTransportServices

cache NIOSSLContext (saves 27k allocs per conn) (#362 )

2021-05-13 12:16:52 +01:00

BestEffortHashableTLSConfiguration.swift

Support request specific TLS configuration (#358 )

2021-05-07 13:47:02 +01:00

Connection.swift

Add defensive connection closure. (#328 )

2021-01-19 17:27:09 +00:00

ConnectionPool.swift

cache NIOSSLContext (saves 27k allocs per conn) (#362 )