4 ms·
those tests there are not using current stuff. The glimmer VM has had loads of perf improvements since those versions. something else to keep in mind is that b
by nullvoxpopuli 7y ago
those tests there are not using current stuff. The glimmer VM has had loads of perf improvements since those versions.
something else to keep in mind is that both the glimmer and ember benchmarks in that test are full framework-level apps. Not just the view layer. This is largely what impacts the startup time and memory usage.
- pier25 7y agoIf that's the case it would be great if the Ember team updated and optimized Ember and Glimmer on those benchmarks. A lot of people in the JS community use those to compare libraries and frameworks. https://github.com/krausest/js-framework-benchmark https://github.com/krausest/js-framework-benchmark
- nullvoxpopuli 7y agoI agree. I believe there are efforts coming to improve perception around these benchmarks.
- pzuraq 7y agoDefinitely agreed. We’ve been focused on optimizing for end-to-end, realistic benchmarks. One of the Ember core team members, Kris Selden, has been working on a testing framework specifically for this actually: https://github.com/TracerBench/tracerbench https://github.com/TracerBench/tracerbench Now that we have a full set of new features, and are comfortable with the performance as a whole, I think we can also start to tune for some microbenchmarks. Our primary concern was to not over optimize for microbenchmarks at the expense of real world performance in real apps, which can happen if you’re not careful.