Keep track of transport latency
Open
- Dominant language
- Java
- Stars
- 12.1k
- Forks
- 4k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Description
@ejona86 [wrote](https://github.com/grpc/grpc-java/pull/2695#issuecomment-278081929):
> Long-term, I question if the transports should just keep track of their latency. They know the latency initially via `SETTINGS` ack and then later via flow control pinging.
Contributor guide
Assessment
This issue has not been assessed yet.