Max Inden

**Status Update** https://github.com/libp2p/test-plans/pull/184 and thus a first iteration of the libp2p performance benchmark setup is merged. Follow-up / future work in tracked in the description of this issue.

Crossposting a Slack message here, for those following through GitHub only. > *First iteration of the libp2p performance benchmarking setup merged* > > More specifically https://github.com/libp2p/test-plans/pull/184. > > Let's try...

**Status Update** > ideally mirror advanced filtering in the URL for better sharing You can now embed the repository and branch of the benchmark data in the dashboard URL. For...

Sorry for the late reply. Generally I am in favor of the move to container registries for their simplicity. That said, I don't have the capacity / priority today to...

If I understand correctly there are two options on how to move forward: 1. Add a dedicated _circuit relay v2_ test, testing compatibility across implementations across all permutations of dialer-relay-listener....

> I am going to start on this spike next week and report the findings here after. //CC @sukunrt since I remember you looking into ways to simulate different network...

This is great news. > Currently I am using a sleep to wait for the listening client successfully complete the reservation. We probably should use redis here same as for...

@Menduist mentioned shadow in the last community call. I checked but dropped it due to missing NAT support https://github.com/shadow/shadow/issues/249.

:rocket: You need to extend https://github.com/libp2p/test-plans/blob/master/multidim-interop/Makefile with your implementation.

I like the approach you are taking here, namely to integrate your new implementation into the interop test-suite early on.