Open Bug 1927438 Opened 1 year ago Updated 1 year ago

[Spike] Investigate usage of default dispatcher instead of main for non UI operations

Categories

(Firefox for Android :: Performance, task, P2)

Product:
Firefox for Android
Component:
Performance
Platform:
All
Android
Type:
task

Tracking

()

People

(Reporter: rsainani, Unassigned)

References

Details

This is based on Bug 1927437. Once that is resolved, the idea is to use default dispatcher to run non UI operations to move load away from main dispatchers. Generally, ui operations should be done on main, IO on IO and other CPU intensive tasks should be done on Default dispatcher.

In the past, within Fenix, it's use has been discouraged because of deadlocks. Deadlocks would be caused if runBlocking is used within default dispatchers, when number of coroutines are more than the number of threads. runBlocking in general should not be used, and suspending APIs should be used. This bug is about investigating that showcasing the impact of moving work from main to default dispatcher, once the relevant runBlocking usages have been removed.

You need to log in before you can comment on or make changes to this bug.