From: Tim Bird <tim.bird@am.sony.com>
To: linux-embedded <linux-embedded@vger.kernel.org>
Cc: linux-kbuild@vger.kernel.org
Subject: Not as much ccache win as I expected
Date: Fri, 13 Jun 2008 12:06:05 -0700 [thread overview]
Message-ID: <4852C51D.30206@am.sony.com> (raw)
I'm running an automated test which does numerous compiles
of the Linux kernel. One of the things I do is create a localversion
file at the root of the kernel source tree with a unique identifier
that I use later on in testing.
I started using ccache to improve the performance of my builds,
but found that the hit rate on the cache was not very good.
$ ccache -s
cache directory /home/tbird/.ccache
cache hit 74416
cache miss 59400
called for link 87252
compile failed 21
not a C/C++ file 143449
no input file 49336
files in cache 42844
cache size 1.8 Gbytes
max cache size 2.0 Gbytes
Thinking that the problem might be having a unique version for
every build (and that this change flowed to every file via the
version.h file), I tried building without this change. I saw
an improvement, but not much.
Is there anything else obvious which is prevents ccache from
working well with a kernel build (that is, anything else that
would, for otherwise identical C files with a similar build,
cause a difference?)
Any tips would be appreciated.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next reply other threads:[~2008-06-13 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 19:06 Tim Bird [this message]
2008-06-13 20:54 ` Not as much ccache win as I expected Oleg Verych
2008-06-13 21:10 ` Tim Bird
2008-06-15 17:58 ` Jörn Engel
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=4852C51D.30206@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.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