New issue
Advanced search Search tips

Issue 714347 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Jan 10
Cc:
llozano@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Investigation of toolchain's running time

Project Member Reported by laszio@chromium.org, Apr 22 2017 
...so as to reducing the overall build / turnaround time.

There are two low-hanging fruits:

1. Build llvm statically. Although it is already much faster after building llvm into a monolithic shared object (from dozens of small libraries), it can be even better to link the executables statically.

2. Compile the toolchain using PGO or AutoFDO.

More to come...

Comment 1 by laszio@chromium.org, Apr 22 2017 

TODOs:

1. Find a representative workload.
2. Apply a bootchart like analysis to the workload to understand how the time is used.

Some random though:
Besides CPU time, I would expect a non-trivial portion of disk IO. It could be beneficial to preload the files if possible.

Comment 2 by benhenry@google.com, Jan 10

Status: Archived (was: Untriaged)
Archiving P3s older than 1 year with no owner or component.
►

Sign in to add a comment