From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ccache: Separate out into its own class
Date: Wed, 30 May 2012 10:33:00 +0100 [thread overview]
Message-ID: <1338370380.20169.112.camel@ted> (raw)
In-Reply-To: <lyr4u3rtpb.fsf@ensc-virt.intern.sigma-chemnitz.de>
On Tue, 2012-05-29 at 15:40 +0200, Enrico Scholz wrote:
> Richard Purdie
> <richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> writes:
>
> > Currently, ccache is used if it is present. When building from scratch
> > it gives no performance improvement
>
> Here, I have a 10% cache hit ratio in a scratch build:
>
> cache hit (direct) 2841
> cache hit (preprocessed) 1370
> cache miss 39957
> called for link 3369
> called for preprocessing 3207
> multiple source files 8
> compile failed 2531
> preprocessor error 432
> couldn't find the compiler 111
> bad compiler arguments 468
> unsupported source language 532
> autoconf compile/link 6613
> unsupported compiler option 132
> no input file 2919
> files in cache 94205
> cache size 2.0 Gbytes
> max cache size 3.0 Gbytes
>
That's good data, thanks for sharing it. In any measurement I've made,
it doesn't seem to help the wall time for the build though :(
We're not removing the ability to use ccache, just changing the way its
enabled which all things considered I still think is a good move...
Cheers,
Richard
prev parent reply other threads:[~2012-05-30 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 12:29 [PATCH] ccache: Separate out into its own class Richard Purdie
2012-05-29 12:36 ` Jason Wessel
2012-05-29 12:48 ` Richard Purdie
2012-05-29 13:40 ` Enrico Scholz
2012-05-30 9:33 ` Richard Purdie [this message]
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=1338370380.20169.112.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox