- When I run with >1 concurrency, I notice that performance for http over libp2p degrades as concurrency goes up, in a manner SIMILAR to graphsync. By contrast pure HTTP stays relatively flat as concurrency goes up.
- This holds true as concurrency goes up to 6, which is the maximum number of simultaneous requests for go-graphsync. If you configure this value higher, it holds true above 6.
Conclussion: I believe the problems may have to do with concurrency scaling with libp2p, or perhaps the way both libp2p over http library and graphsync use libp2p, and, possibly, security encoding on the transport
see k8s compositions below