a run of theverge.com takes 85s

[paulirish]

A few things in here we can look into

• we hit the 45s timeout. though the trace is mostly idle after the first 5s (!!).
• gatherTrace takes 17s!! @exterkamps's core(driver): deliver trace as events rather than a stream #6056 might be our savior here
• if the trace is shorter then lantern and speedline should be faster, but those are certainly taking up a lot of time.
• @patrickhulce looking at idle periods not triggering on this run
• speedline's trace sorting took ~1.25 seconds (longer than calculateVisualProgress!) even though we've already sorted it sort trace events after filtering them paulirish/speedline#70
• replaceIcuMessageInstanceIds adds another ~4 seconds due to running a regex twice over every string value in our report i18n: speed up replacement regex #6072

[paulirish]

gatherTrace takes 17s!! @exterkamps's #6056 might be our savior here

from 17s to 5s. OH YEAHHHHHHHH. 🎊🎊

[brendankenny]

speedline > paulirish/speedline#70

[brendankenny]

replaceIcuMessageInstanceIds > #6072

[patrickhulce]

idle periods not triggering on this run

Core problem here seems to be that for iframe documents we never end up getting a loadingFinished message, just the response received. I'll do a workaround similar to the QUIC situation but should probably look into if this was a recent change or why it was just being masked before.

[paulirish]

with #6078 taken care of, we call this closed.

From 85s ➡️ 16s!

srs team effort. nice one y'all!

[brendankenny]

🎉 🎉