-
Notifications
You must be signed in to change notification settings - Fork 46.5k
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
Create Benchmark Suite #2154
Comments
👍 "Integration Benchmarks" is incredibly hard to pull off meaningfully in just a single number, I think. I imagine it would be great if each "task" was benchmarked separately, so that trade-offs could be properly considered (animation fluidity/stutter, etc) rather than simply seeing the sum of the most costly operations. PS. Also letting browsers breathe between benchmarks, too many benchmarks end up benchmarking mostly the GC under enormous pressure rather than something meaningful. |
Hi, is there some benchmark for "React Core Engine"? |
@trueadm did some work on creating (4) but we haven't used it much. Browser vendors have worked on tests involving React too. I don't think it's likely we'll be spending our time on this so I'll close this. |
We should create a new benchmark suite for patterns that are relevant to React.
We should write test for four different target audiences:
We need to figure out what format to use for all these benchmarks and how easy they are to incorporate into the engines' benchmark suites.
We should also set up a more stable CI environment to track regressions. The one we have now is too noisy.
The text was updated successfully, but these errors were encountered: