Julien Wajsberg

> I'm skeptical this would be fast enough. The browser invokes all of the segmentation and font shaping code paths to make this happen, and doing this for all of...

This stackoverflow entry has a bisecting approach to this problem, like I suggested above: https://stackoverflow.com/a/68395616

Yeah, some of the Timer threads have such markers.

Could the "simple web page" be in-tree instead of something inside profiler.firefox.com? If we don't expect it to change regularly, this could be better.

They are good arguments in favor of having this in the main product indeed, thanks!

The [hotspot tool](https://github.com/KDAB/hotspot) has a nice view that is similar to what Markus suggested: 

Note that the view is sortable both by self time or children-included time.

See also [this butterfly view experiment](https://deploy-preview-1538--perf-html.netlify.com/public/1c77f550d099ab67995681cf835ae589dd88e714/functions/?globalTrackOrder=0-1-2-3&hiddenGlobalTracks=0-1-2&hiddenLocalTracksByPid=58998-0&localTrackOrderByPid=&thread=4&v=3) (where functions are ordered by self time instead of running time like it should)

Here is [the updated butterfly view experiment](https://deploy-preview-2388--perf-html.netlify.com/public/1c77f550d099ab67995681cf835ae589dd88e714/functions/?globalTrackOrder=0-1-2-3&hiddenGlobalTracks=0-1-2&hiddenLocalTracksByPid=58998-0&localTrackOrderByPid=58998-0~&thread=4&v=4), this time using the running time.

Interestingly I thought of that too :-) The tab was a cheap way to get it out but I think we can do better.