how to make a chrome os image with release version of google chrome

[gang]

hi,

I built a chrome os image and saw that the binary size of chrome browser(/opt/google/chrome) is about 234Mbytes, but if I used the partner image from google(https://www.google.com/chromeos/partner/fe/#release) with the same version of chrome os, I found the binary size of chrome browser is about 127Mbytes.  Besides of the binary size difference, there is also significant performance regression happed on the self-built version compared with the partner image.

Here is my steps to build:

$cros_sdk --enter

$export BOARD=xxxx
$./setup_board --board=$BOARD
$./build_packages --board=$BOARD

$./build_image --board=$BOARD --noenable_rootfs_verification test

so any special steps or configuraiton I need take to get a similar release version of goolge chrome as got from part image? Thanks.

[Mike Frysinger]

a large part of the perf issue is probably because we use the AFDO profiles in release builds.  you could try enabling those in your local builds too.

-mike

--
--
Chromium OS discuss mailing list: chromium-os-discuss@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Eugene Rowley]

Have pity on me, as you might tell from the photo, I'm an old... fart.

My experience with unix dates from 1995, and involved about 1 month of work in FORTRAN and SNOBAL in Fairbanks AK and Columbia, SC.  So I am the rawest of n00bs.  

Having said that, I'm looking for suggestions; I'm trying to breathe life into an old Celeron M laptop which hates PUP, and I was hoping to try chromiumOS on it, or chromeOS, to get just some basic work with Google's programs online; or, almost any small word processor.  Looking over your posts, and the DEV docs, I think I can put together a DVD and test it.  Any clue which version might be the best to try?

[gang]

Thanks Mike,

very great suggeton.

After I enabled the AFDO profile, the performance was recovered and the binary size of chrome browser also decreased to about 143Mbytes.

在 2017年4月11日星期二 UTC+8下午2:36:16，Mike Frysinger写道：

a large part of the perf issue is probably because we use the AFDO profiles in release builds.  you could try enabling those in your local builds too.

-mike

On Tue, Apr 11, 2017 at 1:46 AM, gang <w2a...@gmail.com> wrote:

hi,

I built a chrome os image and saw that the binary size of chrome browser(/opt/google/chrome) is about 234Mbytes, but if I used the partner image from google(https://www.google.com/chromeos/partner/fe/#release) with the same version of chrome os, I found the binary size of chrome browser is about 127Mbytes.  Besides of the binary size difference, there is also significant performance regression happed on the self-built version compared with the partner image.

Here is my steps to build:

$cros_sdk --enter

$export BOARD=xxxx
$./setup_board --board=$BOARD
$./build_packages --board=$BOARD

$./build_image --board=$BOARD --noenable_rootfs_verification test

so any special steps or configuraiton I need take to get a similar release version of goolge chrome as got from part image? Thanks.

--
--
Chromium OS discuss mailing list: chromium-...@chromium.org