New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 923540 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Investigate using different ThreadPoolExecutors with different priorities during pre-native startup

Project Member Reported by smaier@chromium.org, Jan 18 (4 days ago)

Issue description

We currently don't use different thread pools in Java - we just have 1 pool at background priority. This would certainly match native better. However, it's unclear how much benefit this would bring, as this pre-native period is short lived. This task should include:

- Measuring how many tasks are actually run before native on a high end and low end phone
- Seeing if there are any early tasks which could benefit from higher priority
- Understanding the difference between scheduling on a thread with higher priority vs scheduling on a thread with lower priority and then temporarily raising the priority while the thread is running


 

Sign in to add a comment