Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Reduce size of WAM build

Fixed

Description

We know Chromium philosophy is not towards adding lots of build options enabling or disabling different paths. Though, there is some margin for reduding the number of GN build tasks, that is now above 53000 items for qemux86.

Also, we are building full chromium browser, though we are not shipping it at all in our targets.

Areas that we expect to get improvement:

  • Remove swiftshader backend.

  • Remove chromium browser and app shell.

  • Only readd app shell for building enact browser or similar.

  • Host compilation of skia or maybe other components... Not sure why we do that.

  • Check if we are building any X11 support at all. That should be dropped.

As a result of this we could reevaluate adding WAM to Qt demos that was discussed in SPEC-4390. Though, it will already give big benefits for our regular builds.

Environment

None

Activity

Show:

Walt Miner 
July 21, 2022 at 7:55 PM

Close for NN Milestone 1

Walt Miner 
June 30, 2022 at 4:30 PM

Thanks. I guess we just leave it on Needlefish. 

José Dapena Paz 
May 31, 2022 at 1:47 PM

I would expect it to be easy to land on Marlin as it is also using m91. About Lamprey, it is using m84. It would need an independent test to try and land similar optimizations.

Walt Miner 
May 31, 2022 at 1:32 PM

Can we cherry pick this to Lamprey and Marlin as well?

José Dapena Paz 
May 20, 2022 at 3:54 PM

Dropping browser, Dawn and swiftshader we reduce 30% of the build units. It is significant both in disk space and build time. If we target also including an app-shell based browser, this would increase a far smaller amount of build units compared to recovering vanilla Chromium.

Details

Assignee

Reporter

Fix versions

Labels

Components

Affects versions

Priority

Created May 20, 2022 at 11:41 AM
Updated July 21, 2022 at 7:55 PM
Resolved June 20, 2022 at 3:32 PM

Flag notifications