[benchmark] Fix benchmark scripts & moved scenarios to correct benchmark project #23058
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue with running scripts in the
material-ui-benchmark
after introducing #22923Also, as agreed in #22923 the scenarios using component rendering are moved to the browser benchmarks, while the the ones which tests only javascript functions are moved to the
material-ui-benchmark
.In addition, the
yarn benchmark
script was renamed toyarn benchmark:browser
to better reflect what the benchmarking is about.