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

Issue 682214 link

Starred by 1 user
Status: Fixed
Owner:
altimin@chromium.org
Closed: May 2018
Cc:
█ hpayer@chromium.org
altimin@chromium.org
haraken@chromium.org
rmcilroy@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
TaskThrottling


Sign in to add a comment

is timer tasks the right queue for v8?

Project Member Reported by jochen@chromium.org, Jan 18 2017 
https://codereview.chromium.org/2589363003 started to use the timer queue for foreground tasks from V8.

Currently, all foreground tasks V8 schedules are GC related, so if we throttle them on background threads, we'll release memory more slowly.

Not sure this is an issue, but it should be taken into account.

Comment 1 by altimin@chromium.org, Jan 18 2017

Owner: altimin@chromium.org
Status: Started (was: Untriaged)
And https://codereview.chromium.org/2638973002/ switched to loading queue due to regression in crbug.com/678286. 

I was planning to expose all three task runners (timer, loading and unthrottled) to PerIsolateData and implement fine-grained control, but given that all tasks posted to V8PerIsolate task queue are foreground and GC-related, just using unthrottled task queue should be fine.

Comment 2 by jochen@chromium.org, Jan 18 2017 

cool, thanks for the update!
I wasn't sure what the status was, and filed this issue mostly so I don't forget about it :)

Comment 3 by altimin@chromium.org, May 23 2018

Status: Fixed (was: Started)
For the sake of history, we've introduced a separate V8TaskRunner for tasks posted from v8.
►

Sign in to add a comment