blog about performance benchmarking in libp2p

[p-shahi]

Draft at https://observablehq.com/@mxinden-workspace/libp2p-perf

[p-shahi]

Imo we should wait to publish the blog post until libp2p/test-plans#261 is resolved and browser transports are added. Thoughts @mxinden ?

[mxinden]

we should wait to publish the blog post until libp2p/test-plans#261 is resolved

Agreed.

and browser transports are added

I don't think the blog post needs to be block on browser transports. We already have more content than a single post can hold. We likely need multiple posts anyways. Browser transports can be one in a series of many.

[marten-seemann]

and browser transports are added

I don't think the blog post needs to be block on browser transports. We already have more content than a single post can hold. We likely need multiple posts anyways. Browser transports can be one in a series of many.

I agree, we don't need to wait for the browser transports.

I'd suggest to wait until we've patched our stacks (at the very least, Go and Rust) to achieve decent transfer speeds (let's say 80% of the iPerf result).