1626666 - Rework the ipc profile counters

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect, P3)

Description

[Nicolas Silva [:nical]]

Currently IPC profile counters give a mix of useless, useful and ambiguous information:

• consume time merely the time it takes to push something into a vector (always displays zero)
• total IPC time contains the time between api.set_display_list and the render backend picking the message up, plus the time it took to build the display list (but doesn't take into account the time it took for actual IPC in between).
• send time is only the time between api.set_display_list and the render backend picking the message up but doesn't take into account the time it took between the content process and the compositor thread sending the display list.

Comment 1

[Nicolas Silva [:nical]]

Attachment: Bug 1626666 - Rework the ipc profile counters. r=jrmuizel,Bert,gw

Before this patch:

• Consume time merely is the time it takes to push something into a vector (always displays zero).
• Total IPC time and the DisplayList IPC graph measure the time between api.set_display_list and the render backend picking the message up, plus the time it took to build the display list (but doesn't take into account the time it took for actual IPC in between).
• Send time is only the time between api.set_display_list and the render backend picking the message up but doesn't take into account the time it took between the content thread sending the DL and the compositor thread forwarding it.

After this patch:

• Content send time measures the time between the content thread sending the display list and the compositor forwarding it (actual IPC).
• Api send time measures the time between the compostor thread forwarding the DL and the render backend picking it up.
• Consume time is removed.
• Total send time is the sum of content and api times.
• Display list build times and display list IPC (total send time) are on separate graphs.

Depends on D69227

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ea22f0b1e2a0
Rework the ipc profile counters. r=Bert,gw

Comment 3

[Nicolas Silva [:nical]]

Attachment: Bug 1626666 - Ensure ipc profile counters follow transactions through the scene builder thread. r=jrmuizel

Instead of collecting so-called ipc counters when receving the SetDisplayList on the render backend, pass the information through the scene builder thread and update the profile on the render backend after the scene is swapped. This prevents ipc counters to be displayed while the transaction is still being processed by the scene builder thread.

Comment 4

[Nicolas Silva [:nical]]

Attachment: Bug 1626666 - Rename IpcProfileCounters into TransactionProfileCounters. r=jrmuizel

Few of the counters actually have anything to do with IPC although they all relate to events of layout transactions.

Depends on D69414

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/1a729c8ea631
Ensure ipc profile counters follow transactions through the scene builder thread. r=jrmuizel
https://hg.mozilla.org/integration/autoland/rev/d2771cdff401
Rename IpcProfileCounters into TransactionProfileCounters. r=jrmuizel

Comment 6

[Stefan Hindli [:stefan_hindli]]

https://hg.mozilla.org/mozilla-central/rev/ea22f0b1e2a0
https://hg.mozilla.org/mozilla-central/rev/1a729c8ea631
https://hg.mozilla.org/mozilla-central/rev/d2771cdff401