-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
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
Move benchmark/README.md to doc/guide #11190
Comments
I think it makes sense to have a README that explains how to run the benchmarks in the benchmarks directory, but I do think that the guide on how to write one should be in guides (linked from the readme) |
I agree, the same can be done to test/README.md too. I'll prepare a PR for that :) |
* Write a new benchmark/README.md describing the benchmark directory layout and common API. * Fix the moved benchmarking guide accordingly, add tips about how to get the help text from the benchmarking tools. PR-URL: #11237 Fixes: #11190 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Andreas Madsen <amwebdk@gmail.com>
* Write a new benchmark/README.md describing the benchmark directory layout and common API. * Fix the moved benchmarking guide accordingly, add tips about how to get the help text from the benchmarking tools. PR-URL: #11237 Fixes: #11190 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Andreas Madsen <amwebdk@gmail.com>
The current
benchmark/README.md
is in fact a guide on how to run and write benchmarks, I suggest we move this to doc/guides (wherewriting-tests.md
is) and create another README.md that explains the directory layout/common API (like whattest/README.md
does).cc @nodejs/collaborators
The text was updated successfully, but these errors were encountered: