From 2cb8a4689422c8cddf51f09620d699f56e9d8111 Mon Sep 17 00:00:00 2001 From: 0x676e67 Date: Fri, 24 Jan 2025 12:06:26 +0800 Subject: [PATCH] docs: update performance information --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index c26f0ae8..666e0ab6 100644 --- a/README.md +++ b/README.md @@ -122,6 +122,8 @@ As synchronous APIs are not actively maintained due to time constraints, only as `BoringSSL` is a fork of `OpenSSL` that is designed to be more secure and efficient. It is used by Google Chrome and Android, and is also used by Cloudflare. In addition to that, regarding the TLS parrot echo issue in Firefox, we haven’t encountered any serious problems with `BoringSSL` related to Golang [utls issue](https://github.com/refraction-networking/utls/issues/274). +By default, `HTTP2` tracing is turned off, which will reduce the performance overhead by 15%. For more information, see issue: + ## Connection Pool Regarding the design strategy of the connection pool, `rquest` and `reqwest` are implemented differently. `rquest` reconstructs the entire connection layer, treating each host with the same proxy or bound `IP`/`Interface` as the same connection, while `reqwest` treats each host as an independent connection. Specifically, the connection pool of `rquest` is managed based on the host and `Proxy`/`IP`/`Interface`, while the connection pool of `reqwest` is managed only by the host. In other words, when using `rquest`, you can flexibly switch between proxies, `IP` or `Interface` without affecting the management of the connection pool.