Florian Quèze
Florian Quèze
Example profile: https://share.firefox.dev/3mtg0JD  Quick discussion with the team gives me the impression that this isn't the intended behavior.
When looking at this profile https://share.firefox.dev/3qYuANm, I would like to be able to see quickly all the DOM event relating to the browser.xhtml window I think the UI could be...
Example profile using these new types: https://share.firefox.dev/3Vsc6p8, [deploy preview](https://deploy-preview-4941--perf-html.netlify.app/public/4atjf37gg5b04jnqj1jt6peeqmy02hnta6qarxg/marker-chart/?globalTrackOrder=502134&hiddenGlobalTracks=2&hiddenLocalTracksByPid=19665-0wbdwxqxtwy2~19799-013wqswv~25685-0wp~29948-0wnqwu~19746-0wmowq&markerSearch=19665&thread=0&v=10)
I think the right place to document power profiling would be a new page in the advanced topic section: https://profiler.firefox.com/docs/#/./advanced-topics ┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-650)
For Eleventy sites with templates using shortcodes that do a lot of computation, rendering the template is the part of the build that takes the longest. This part is done...
Steps to reproduce: 1. Capture or load a profile that has 2 processes that start having samples at different times (this can often happen if one process is very active...
Steps to reproduce: * load https://share.firefox.dev/3lXGUsO * select the third row in the marker table. * click the permalink button, copy that url and load it. Expected result: the same...
Here are 2 profiles of building the same website, first [without the PR](https://share.firefox.dev/4bhBtP6), and then [with the PR](https://share.firefox.dev/3Wlxqgd). With the PR, `getHash` takes 3.1% (30.7ms) of the total build time....
Just a WIP to share the code and have a deploy preview for feedback. Flow and tests don't pass (yet). For https://profiler.firefox.com/public/k56pyq04p6yey31fxez6gex1ab53avx14ghmsb8/ (a power profile coming from the gecko profiler...
Example profiles: https://share.firefox.dev/3Uew1GI Probably just a matter of adjusting the word-wrap CSS property somewhere. ┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-809)