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.
@sorrycc hi , Farm
api
andhmr
usage issues are solved in the new version, now you can run thefull benchmark
.Again, farm enables
caching
by default when starting theserver
orbuild
, and the time it takes to write files is huge, so according to mako benchmark project, we need to close caching in the farm test. The time to write to the server is about 40% of the project startup time. I hope you can retest this benchmark. ,gratefulIn addition, I think there is a problem with all existing benchmark tests (this also exists in the farm benchmark test. We will summarize it after adding mako test in the future), which is the different target time and backup size. I think we should establish a standard in the future. For specific enviroment (browser or node), We may add
various polyfills
according to different products. we can establish a unified standard based on https://github.com/browserslist/browserslist and conduct benchmark tests for specific environments.#1