[OE-core] [PATCH 1/4] sstate: Add extra directory level
Peter Kjellerstedt
peter.kjellerstedt at axis.com
Wed Jan 8 03:53:38 UTC 2020
> -----Original Message-----
> From: openembedded-core-bounces at lists.openembedded.org <openembedded-core-
> bounces at lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 6 januari 2020 01:44
> To: akuster808 <akuster808 at gmail.com>; openembedded-
> core at lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/4] sstate: Add extra directory level
>
> On Sun, 2020-01-05 at 16:41 -0800, akuster808 wrote:
> > On 1/5/20 4:06 PM, Richard Purdie wrote:
> > > We're having speed issues on the autobuilder due to the numbers of
> > > files in sstate
> > > directories. We previously split these by the first two characters
> > > of the hash.
> > > This change extends this to split by the next two characters as
> > > well, creating
> > > more layers of directories.
> > >
> > > This should signifiantly speed up eSDK builds on the autobuilder as
> > > the current
> > > sstate layout simply isn't scaling there but addresses a general
> > > complaint.
> > >
> > > gen-lockedsig-cache needed to be updated for the new split level
> > > sstateI.
> >
> > I assume zeus worthy?
>
> I think we need to discuss that. It is a fairly significant change in
> behaviour.
>
> Options are:
>
> a) none of these
> b) only this first change
> c) all of them if we want to fix the 255 char sstate filename limit
> issue
>
> Cheers,
>
> Richard
I would like to see at least the first patch being backported. You are
not alone with huge sstate-cache directories...
We have not had the problems solved by the other three patches so for
us at least, they are not required. And they do seem somewhat invasive.
//Peter
More information about the Openembedded-core
mailing list