WIP: Allow external HTTP client (Aerogramme testing) #731

Draft

quentin wants to merge 1 commits from k2v/shared_http_client into main

quentin commented

2024-02-23 16:13:19 +00:00

Owner

Excerpt of a blog post on Aerogramme to come:

Another concern is the RAM consumption with the IDLE feature. The real cause is that we retain in-memory the full user profile (mailbox data, IO connectors, etc.): we should instead keep only the minimum data to be waken-up. That's the ideal fix, the final solution, that would take lots of time to design and implement. This fix is not necessary now, instead we can simply try to optimize the size of a full user profile in memory. On this aspect, the aws-sdk-s3 crate has the following note:

Client construction is expensive due to connection thread pool initialization, and should be done once at application start-up.

Digging deeper in the crate dependencies, we learn from the aws-smithy-runtime crate, we can read:

[Constructing] a Hyper client with the default TLS implementation (rustls) [...] can be useful when you want to share a Hyper connector between multiple generated Smithy clients.

But I also need to share an HTTP Client for my K2V session if I want to correctly benchmark Aerogramme.
That's why I am extending K2V to share an HTTP Client.

Not sure it will work or will improve anything, so no need to merge for now.
Just testing...

Excerpt of a blog post on Aerogramme to come: --- Another concern is the RAM consumption with the IDLE feature. The real cause is that we retain in-memory the full user profile (mailbox data, IO connectors, etc.): we should instead keep only the minimum data to be waken-up. That's the ideal fix, the final solution, that would take lots of time to design and implement. This fix is not necessary now, instead we can simply try to optimize the size of a full user profile in memory. On this aspect, the aws-sdk-s3 crate has the following note: > Client construction is expensive due to connection thread pool initialization, and should be done once at application start-up. Digging deeper in the crate dependencies, we learn from the aws-smithy-runtime crate, we can read: > [Constructing] a Hyper client with the default TLS implementation (rustls) [...] can be useful when you want to share a Hyper connector between multiple generated Smithy clients. --- But I also need to share an HTTP Client for my K2V session if I want to correctly benchmark Aerogramme. That's why I am extending K2V to share an HTTP Client. Not sure it will work or will improve anything, so no need to merge for now. Just testing...

quentin added 1 commit 2024-02-23 16:13:19 +00:00