Repo project-objects is huge |
|
Issue description.repo/project-objects is ~36G. This is mostly git history; a shallow sync is only <5G. Top culprits: intel-fsp: >6G kernel: >5G chromeos-overlay: >3G various vendor kernels: >6G total There are a number of things we could do to reduce this size for various common cases (esp. non-platform developers and CI): 1. don't load all of these projects by default (groups="notdefault") 2. make shallow checkouts of some of the largest repos (clone-depth="1") 3. provide a non-default manifest.xml that extends projects with one of the above options
,
Sep 24
> is this a fresh checkout or are you looking at an existing checkout The above numbers were from an existing checkout; in a fresh checkout .repo is ~25G. intel-fsp: ~5G chromeos-overlay: ~3G kernel: ~2G
,
Sep 24
the kernel is going to be big, no way around that as long as we keep having multiple checkouts (3.8/3.10/3.14/3.18/4.4/4.14/4.19). the fsp looks excessive, but i think we don't have too much control over that either -- it's internal code for intel bringup. iiuc, we shouldn't need to keep those in the manifest once development for that platform has forked for firmware. doesn't look like we've shipped cnl/glk/icl (yet?), so having those in the checkout is to be expected if unfortunate. chromiumos-overlay i would have expected to be smaller because we set sync-c=true for that repo ... but i don't know what the current master-only history is for it. |
|
►
Sign in to add a comment |
|
Comment 1 by vapier@chromium.org
, Sep 21