New issue
Advanced search Search tips

Issue 791566 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Jan 11
Cc:
chromeos-performance-bugs@google.com
chrome-perf-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: ----
Type: Bug



Sign in to add a comment

Speed: restricted number of software raster threads on Arm ChromeOS devices

Project Member Reported by jonathan...@arm.com, Dec 4 2017 
On Arm big.LITTLE SoCs, the number of raster (CompositorTileWorker) threads is limited to a maximum of 2.

On ChromeOS, setting the number of raster threads to the total number of cores in the SoC enables a significant performance gain on Motionmark and a smaller gain on Page Cycler.

Comment 2 by brucedaw...@chromium.org, Dec 4 2017 

 Issue 791562  has been merged into this issue.

Comment 3 by krajshree@chromium.org, Dec 5 2017

Labels: OS-Chrome
The issue is related to OS-chrome. Hence, adding appropriate label.

Comment 4 by vsu...@google.com, Jan 10 2018

Components: OS>Kernel>Graphics
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 11

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment