Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

a run of theverge.com takes 85s

See original GitHub issue

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 #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 https://github.com/paulirish/speedline/pull/70
replaceIcuMessageInstanceIds adds another ~4 seconds due to running a regex twice over every string value in our report #6072

Issue Analytics

State:
Created 5 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

patrickhulcecommented, Sep 20, 2018

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.

1reaction

paulirishcommented, Sep 19, 2018