Closed Bug 1078136 Opened 6 years ago Closed 6 years ago

Tune the thread priority for VsyncDispatcher thread

Categories

(Core Graveyard :: Widget: Gonk, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jerry, Unassigned)

References

Details

In Bug 1062117, we can set the thread priority for VsyncDispatcher thread. We should check the effect for app launch time, load time and other performance issue when we raise the thread priority.
I assume that this is the VsyncDispatcher thread, not the android hardware vsync thread correct? The VsyncDispatcherThread should only send a message from chrome process / VsyncDispatcher Thread -> Content Process / main thread. I think the biggest bottleneck here will be that the content process is busy. I've measured sending messages from chrome -> content IPC before, and most of the delay is on the child process side, so I'm not sure how much we need this at the moment. Much of the data is in bug 991420.
With the current silk architecture, there is no separate vsync dispatcher thread, only the hardware vsync thread. Closing as WFM.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.