We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As discussed in pl-strflt.notion.site/js-libp2p-perf-benchmarking-f7c42f96cbd44799a321347f6c15c8d4?pvs=4
In order to detect performance regressions at the component level, it may be useful to run component level benchmarks per PR. We've seen scenarios where mplex is more performant than yamux, despite mplex being deprecated. We could leverage the existing perf implementation and a Github action to create a comment such as this one ChainSafe/lodestar#6004 (comment)
The text was updated successfully, but these errors were encountered:
protocol-perf
Add similar benchmarking that lodestar has but at the component level.
Sorry, something went wrong.
No branches or pull requests
As discussed in pl-strflt.notion.site/js-libp2p-perf-benchmarking-f7c42f96cbd44799a321347f6c15c8d4?pvs=4
In order to detect performance regressions at the component level, it may be useful to run component level benchmarks per PR. We've seen scenarios where mplex is more performant than yamux, despite mplex being deprecated. We could leverage the existing perf implementation and a Github action to create a comment such as this one ChainSafe/lodestar#6004 (comment)
The text was updated successfully, but these errors were encountered: