Max Inden 73dbde1519 refactor(perf): expose single latency measurement ...

Instead of exposing the time to establish a connection, the time to upload the bytes and the time to download the bytes, expose a single time including all three.

The rational here is, that differentiation of the three is flawed. E.g. when does one stop the upload timer and start the download timer? When the last byte is sent? When the last byte is flushed? When the first byte is received?

See https://github.com/libp2p/test-plans/pull/184#pullrequestreview-1482600521 for past discussion.

Pull-Request: #4105.


  
Co-Authored-By: Max Inden <mail@max-inden.de>

2023-06-26 03:56:17 +00:00

..

bin

refactor(perf): expose single latency measurement

2023-06-26 03:56:17 +00:00

client

feat(swarm): replace address scoring with explicit candidates

2023-05-24 07:52:16 +00:00

server

feat(swarm): replace address scoring with explicit candidates

2023-05-24 07:52:16 +00:00

client.rs

refactor(perf): use libp2p-request-response

2023-05-28 05:51:53 +00:00

lib.rs

refactor(perf): use libp2p-request-response

2023-05-28 05:51:53 +00:00

protocol.rs

refactor(perf): use libp2p-request-response

2023-05-28 05:51:53 +00:00

server.rs

refactor(perf): use libp2p-request-response

2023-05-28 05:51:53 +00:00