Open Bug 1603302 Opened 4 years ago Updated 2 years ago

Slow layout on longer WebSocket tables

Categories

(DevTools :: Netmonitor, defect, P3)

Product:
DevTools
Component:
Netmonitor
Type:
defect

Tracking

(Performance Impact:low)

Project Flags:
Performance Impact low

People

(Reporter: Harald, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf, perf:responsiveness)

What were you doing?

  1. Open Network panel and load https://firefox-devtools-debug-ws.glitch.me/
  2. Select WS connection and the Messages tab to see WS frames
  3. Move the mouse to generate 500

What happened?

https://perfht.ml/35bjzMk

36ms reflow on each new message being added.

What should have happened?

500 rows table doesn't seem that much of a stress test and should be best.

How do I "generate 500"? Moving mouse doesn't seem to do much.
But anyhow, qf:p3, given that this is devtools which shouldn't be open normally.

Whiteboard: [qf] → [qf:p3:responsiveness]

A better use case, just sign in to http://tankanarchy.herokuapp.com/ , which creates 1+ messages per frame.

Flags: needinfo?(bugs)

Back to [qf] so that this gets re-evaluated, but I assume still p3, since this is devtools.

Flags: needinfo?(bugs)
Whiteboard: [qf:p3:responsiveness] → [qf]
Whiteboard: [qf] → [qf:p3:responsiveness]
Performance Impact: --- → P3
Keywords: perf:responsiveness
Whiteboard: [qf:p3:responsiveness]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.