From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Sharing sstate
Date: Tue, 27 Sep 2011 17:17:00 +0100 [thread overview]
Message-ID: <1317140228.26109.164.camel@ted> (raw)
In-Reply-To: <4E81DC24.8020307@mlbassoc.com>
On Tue, 2011-09-27 at 08:22 -0600, Gary Thomas wrote:
> I'd really like to be able to share sstate effectively. One problem I have with
> it is the size - for a build of my system (something similar to core-image-sato
> on BeagleBoard), the sstate cache for a build-from-scratch is nearly 5GB! Not
> exactly simple to share across sites.
>
> It seems to me that maybe I don't need to share everything. For example, the
> webkit-gtk package:
>
> $ ls -l sstate-cache/*webkit-gtk*
> -rw-rw-r-- 1 gary gary 331221793 Sep 23 16:21
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-4a04fc210c0a565767a2ad9bb11d8322_deploy-ipk.tgz
> -rw-rw-r-- 1 gary gary 12740 Sep 23 16:21
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-4a04fc210c0a565767a2ad9bb11d8322_deploy-ipk.tgz.siginfo
> -rw-r--r-- 1 gary gary 326376172 Sep 23 16:15
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-67b4ac238844551dd48eed3255ea33d0_populate-sysroot.tgz
> -rw-r--r-- 1 gary gary 21652 Sep 23 16:15
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-67b4ac238844551dd48eed3255ea33d0_populate-sysroot.tgz.siginfo
> -rw-r--r-- 1 gary gary 665832323 Sep 23 16:19
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-726c31c08826bf24e6db77fdf5f4408b_package.tgz
> -rw-r--r-- 1 gary gary 98746 Sep 23 16:19
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-726c31c08826bf24e6db77fdf5f4408b_package.tgz.siginfo
> -rw-rw-r-- 1 gary gary 3117 Sep 23 15:38
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-f9267d59a61b218bd6ab76ed55f12e8e_populate-lic.tgz
> -rw-rw-r-- 1 gary gary 8359 Sep 23 15:38
> sstate-cache/sstate-webkit-gtk-armv7a-vfp-neon-amltd-linux-gnueabi-1.5.1+svnr90727-r0-armv7a-vfp-neon-2-f9267d59a61b218bd6ab76ed55f12e8e_populate-lic.tgz.siginfo
>
> Would it be possible to only share part of this, maybe the "package" file?
> It seems to me that this could make the needed (shared) cache much smaller...
The build will only use the pieces it needs. If your build only needs
the deploy-ipk pieces and doesn't need to write new packages files it
can survive without the package part. If it doesn't need to compile
something against webkit, it won't use the populate-sysroot file.
So what I'm saying is you likely could get away with not sharing the
*_package files at least. The only downside is if you turn on rpm
packaging it would have to rebuild.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-27 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 14:22 Sharing sstate Gary Thomas
2011-09-27 16:17 ` Richard Purdie [this message]
2011-09-28 2:25 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2015-03-26 13:44 Gary Thomas
2015-03-26 23:13 ` Gary Thomas
2015-03-27 7:46 ` Mike Looijmans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1317140228.26109.164.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.