JebJan 26, 2023
Apparently, in @ChromeDevTools there is a way to break down the "Compile Code" phase into "Compile" and "Parse".
The only problem is that it doesn't work 😕.
#webperf
Show threadJeb
So according to @addyosmani and this article https://web.dev/optimizing-content-efficiency-javascript-startup-optimization/ you should see it if you enable experimental feature `Timeline: V8 Runtime Call Stats on Timeline`. I did just that and nothing changed. Is this still a thing? Does it work for anyone else?
JavaScript Start-up Optimization

Keep your network transmission and parse/compile cost for JavaScript low to ensure pages get interactive quickly.

web.dev
Jan 26, 2023 at 2:28pmWeb
Show threadJebJan 26, 2023
Luckily you can get this info (although with lot's of other noise) by enabling "Timeline: show all events".
Show threadJebJan 26, 2023
Doing this should give you the breakdown.
Show threadJebJan 26, 2023
Btw, I'm still struggling to interpret this. So the script evaluation starts with `ParseFunction` method that takes 1ms (self) and the `ParseFunction` calls my code which takes 181ms? So what took long time here, the parsing or the execution?
@yoavweiss @nomsternom any idea?