Connection pool in tonic?

[YjyJeff]

According to the documentation of Channel : It is based on hyper::Client, the hyper::Client has a connection pool to for better performance. Therefore, we do not need the connection pool for tonic. However, after reading the source code of the Channel, I found that it is based on the HttpConnector, which does not support connection pool, as far as I know....

So, for better performance, do we still need a connection pool for tonic? Maybe using the hyper::Client as an underling implementation is better?

Thanks in advance, sincerely~

[LucioFranco]

Tonic uses the lower-level client from hyper https://github.com/hyperium/tonic/blob/master/tonic/src/transport/service/connection.rs#L5 and does not use its connection pool.

[YjyJeff]

Thank you for your reply~

According to the tonic-wrap example, we can use the high-level client from hyper: hyper::Client to do the same thing. So, what is the advantage of the lower-level client in tonic? And in which situations should I prefer to use hyper::Client? Thanks~

[LucioFranco]

It all depends on your setup, the tonic client aligns better with regular gRPC clients while the hyper one is more general.

[YjyJeff]

Got it, thanks~