summaryrefslogtreecommitdiffstats
path: root/apps
diff options
context:
space:
mode:
authorericrk <ericrk@chromium.org>2015-12-18 14:04:04 -0800
committerCommit bot <commit-bot@chromium.org>2015-12-18 22:04:57 +0000
commit5a1188c6c3b464ed96694881dfec6c70c7d58a29 (patch)
tree6e8df52d2dd12e8547e18c1330666f892dc60a4a /apps
parent56313bcb00c1e44b27daa0b2da994ca2dd2b6944 (diff)
downloadchromium_src-5a1188c6c3b464ed96694881dfec6c70c7d58a29.zip
chromium_src-5a1188c6c3b464ed96694881dfec6c70c7d58a29.tar.gz
chromium_src-5a1188c6c3b464ed96694881dfec6c70c7d58a29.tar.bz2
TaskGraphRunner Group support
Adds a group to TaskGraphRunner, this can be used by an implementation along with priority in order to decide how to execute tasks. This is a prerequisite patch for thread affinity changes which are coming in a follow-up. This patch causes a moderate (~15%) regression in cc_perftests for TaskGraphRunner. The main regressions I'm seeing are: In ScheduleTasks, we're seeing an additional 3% time spent in operator[] for the two new maps vs ToT. We're also seeing an additional 5.5% of time spent in test code which builds the task graph. Other regressions are less clear, but probably have to do with the additional cost of ScheduleTasks in the function body itself (inlined looping). BUG= CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel CQ_INCLUDE_TRYBOTS=tryserver.chromium.win:win_chromium_gn_x64_rel Committed: https://crrev.com/05ca4bc9df381e6345f9cf7ee29cdfa075be30c4 Cr-Commit-Position: refs/heads/master@{#365140} Committed: https://crrev.com/3b4338fc32cf20703baa8066bdad7ce07c5ae696 Cr-Commit-Position: refs/heads/master@{#365646} Review URL: https://codereview.chromium.org/1489233003 Cr-Commit-Position: refs/heads/master@{#366180}
Diffstat (limited to 'apps')
0 files changed, 0 insertions, 0 deletions