From: Jan Kiszka <jan.kiszka@siemens.com>
To: Roman Stratiienko <roman.stratiienko@globallogic.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [PATCH] ci: Tune config
Date: Wed, 10 Apr 2019 15:58:07 +0200 [thread overview]
Message-ID: <72eac2b9-75ce-2648-b779-e6833df4cd3e@siemens.com> (raw)
In-Reply-To: <CAODwZ7ut3DGL9fq4yEFNMygUWJvXjW0xdGof7CvTAKFU0TJr4w@mail.gmail.com>
On 10.04.19 10:42, Roman Stratiienko wrote:
> I did measurements after clearing cache 'ccache -C'
>
> I assume that 600mb in current statistic is due to multiple build of different
> source dependencies due to enabled DEBUG INFO config. Old cache should be
> invalidated and cleaned automatically as size goes up to the limit.
>
Indeed, things piled up.
We can keep the lower limit for now and see how this evolve.
Jan
>
> ср, 10 апр. 2019 г., 08:34 Jan Kiszka <jan.kiszka@siemens.com
> <mailto:jan.kiszka@siemens.com>>:
>
> On 09.04.19 22:47, Roman Stratiienko wrote:
> >
> > I have similar issue some time ago on another project, but due to lack of
> time
> > and low priority it was unsolved.
> > And you've found the root cause and it is great, thanks!.
>
> At least it looks like as the rebuild no only takes 15 minutes.
>
> >
> > I did some measurements of ccache size, and results is following:
> > - 4.14 arm64 - cache size - 232.7 MB
> > - 4.19 arm - cache size - 246.4 MB
> > - Others are even less.
> >
> > So I suggest to left it 400MB, thus not to use too much disk space of
> travis's
> > servers.
>
> Look at the statistics you added to our build:
>
> 4.14 arm64: 601.6 MB
> 4.19 arm: 557.7 MB
> 4.14 x86: 292.5 MB
>
> If you cap the size, ccache may drop artifacts during the build, then refill,
> but may stay below the limit at the end. Still, the cache will be incomplete.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-04-10 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 19:37 [PATCH] ci: Tune config Jan Kiszka
2019-04-09 20:47 ` Roman Stratiienko
2019-04-10 5:34 ` Jan Kiszka
2019-04-10 8:42 ` Roman Stratiienko
2019-04-10 13:58 ` Jan Kiszka [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=72eac2b9-75ce-2648-b779-e6833df4cd3e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=roman.stratiienko@globallogic.com \
--cc=xenomai@xenomai.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.