Closed Bug 956452 Opened 11 years ago Closed 6 years ago

Network monitor is janky on sites with a ton of requests

Categories

(DevTools :: Netmonitor, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1487906

People

(Reporter: fitzgen, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [netmonitor-reserve])

Attachments

(2 files, 1 obsolete file)

Attached image screen shot of profile (obsolete) —
For example, https://soundcloud.com/stream had 691 requests for me, and once all the requests started finishing and getting responses, we started janking pretty hard. I'm pretty sure this is the drawing of the waterfall graph. Is it possible to do this in a |DevToolsUtils.yieldingEach| loop or move a bunch of processing to a worker? (Profile was too big to upload, but I have a screenshot.)
Flags: needinfo?(vporof)
I'm reasonably sure we could.
Flags: needinfo?(vporof)
Is it still janky for you now with the new theme changes?
Flags: needinfo?(nfitzgerald)
Attached image screenshot of profile
(In reply to Victor Porof [:vporof][:vp] from comment #2) > Is it still janky for you now with the new theme changes? Yup, although I had to manually clear the cache so that all the avatar requests would happen again on soundcloud; Cmd-Shift-R wasn't cutting it. Here is a screenshot of the up to date profile.
Attachment #8355709 - Attachment is obsolete: true
Flags: needinfo?(nfitzgerald)
Thanks!
Nick, you know that you can click 'Save' to export the profile and attach it to the bug, right?
(In reply to Panos Astithas [:past] from comment #5) > Nick, you know that you can click 'Save' to export the profile and attach it > to the bug, right? Yeah but that only works with small profiles. Bugzilla's file size limit is like 10 or 20 mb and the profiles can easily double or triple that.
I guess that could be a problem, although I've never created anything larger than a couple of MB compressed myself.
I happened to run this with packet logging enabled, and it was logging *tons* of 'substring' requests, containing lots of base64-encoded stuff.
Here is the tail end of the packet log. I've cleaned it up a bit by taking out the actual string contents.
Is it still slow now that bug 1064262 landed?
Whiteboard: [netmonitor]
Flags: qe-verify?
Priority: -- → P3
Whiteboard: [netmonitor] → [netmonitor-reserve]
Flags: qe-verify? → qe-verify+
Priority: P3 → P1
QA Contact: ciprian.georgiu
Product: Firefox → DevTools
Since the orignal report of this bug, the netmonitor has been almost completely rewritten. * We do throttle UI updates to avoid DOM operations on each new request. * all request's data that isn't display in the default table is now lazy loaded, so that the RDP overhead is much lower. * many optimizations have been made to make the table layout faster to render. I don't have any soundcloud account. Is it still slow?

Main thread impact got a lot better. We have more actionable bugs open, so duping this for the meta bug 1487906.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: