There’s another benchmark suite named Speedometer, that was created by Apple in 2014, which shows a profile that is closer to what actual web pages look like. The benchmark consists of the popular TodoMVC application implemented in various web frameworks (i.e., React, Ember, and AngularJS).
Find this article and much more in...
Survey findings from over 500 developer responses
Articles written by top Performance experts
"What Ails Your Application" Infographic
Directory of performance optimization and monitoring tools
You can now see parsing and compile buckets in the profiler. And, over the last few years, we’ve introduced another mechanism — called chrome://tracing — which allows you to record traces that collect all kinds of events. For example, you can analyze in detail how much time V8 spends in the different parsing steps, and thereby understand whether it might make sense to consider using a tool like optimize-js to mitigate the overhead of pre-parsing when it’s not beneficial, for example, the function is executed immediately anyway.
Chrome Tracing provides you with a pretty detailed understanding of what’s going on performance-wise by offering a view into the less obvious places. V8 has a step-by-step guide on how to use this. For most use cases, though, I’d recommend sticking to the Developer Tools, because they offer a more familiar interface and don’t expose an overwhelming amount of the Chrome/V8 internals. But for advanced developers, chrome://tracingmight be the swiss army knife that they were looking for.
Since not all browsers support all new language features, there’s a certain period of time where new features require transpilation. But if you are building a web application today, consider shipping as much of the original code as possible. An Intranet application with dedicated clients inside the company, all using some recent browser version, could as well be written and shipped as ES2015 code.