Closed Bug 1156591 Opened 5 years ago Closed 5 years ago

Add Profile markers for async tab switch performance profiling

Categories

(Firefox :: Tabbed Browser, defect)

x86
All
defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 40
Tracking Status
e10s + ---
firefox40 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

We should add a marker in the parent process just as we set a tab into the STATE_LOADING state, and just after we hear the MozLayerTreeReady event. We should also add one in the tab switcher's updateDisplay method where we actually update the selectedIndex on the tabpanels.

We should also add a marker in LayerTransactionParent::RecvUpdate, on entry into the method, and just before mShadowLayersManager->ShadowLayersUpdated is called.

In the content process, I suspect there are places we should add markers in ShadowLayers.cpp. I can ask around for Graphics input on where those places would be.
So I laid out some markers in comment 0, but I actually think something simpler will suffice given what Telemetry we started to gather in bug 1156592.
Assignee: nobody → mconley
Status: NEW → ASSIGNED
Attachment #8600356 - Flags: review?(felipc)
Attachment #8600356 - Flags: review?(felipc) → review+
https://hg.mozilla.org/mozilla-central/rev/c72beadc2bc6
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
You need to log in before you can comment on or make changes to this bug.