Create test to show libp2p's performance compared to http

Done Criteria

We have benchmarks that shows the performance of libp2p using various transports/muxers in real world conditions compared to something standard in the web2 world like HTTP.

Why Important

Questions come in on, "why use libp2p and protocols build on top instead of something like http? Isn't http faster?" Ideally we should have data showing where libp2p transports/muxers stand.

User/Customer

Developers determining whether libp2p will be placing performance overhead, which can affect their decision to adopt libp2p as a whole.

Notes

1. Initial focus is on go-libp2p but ideally other libp2p implementations can be added.
2. https://github.com/filecoin-project/data-transfer-benchmark is likely a good place to start from.
3. Minimum set of results is:

• http
• http over libp2p using TCP/Yamux
• http over libp2p using QUIC

4. When tests are run locally, we need to make sure an appropriate MTU is set: https://github.com/testground/testground/issues/1385
5. Ideally though tests can be run against two distinct nodes sending traffic over the internet, which is the real world conditions we want to compare against. https://github.com/testground/testground/pull/1425 or https://github.com/testground/testground/issues/1392 is needed for this.

Start by reviewing the data-transfer-benchmark project and the Testground issue #1385 plus PR #1425 or issue #1392. Define benchmark runs for HTTP, HTTP over libp2p TCP/Yamux, and HTTP over libp2p QUIC, using an appropriate MTU locally and distinct internet-connected nodes where supported. Done means reproducible results covering the requested transports and real-world conditions.