03.06.2024 14:29, Daniel P. Berrangé wrote:
Given your original job had cache of 447 MB, and new cache is 654 MB, the
old cache is 68% of size of the new cache. So effectively your 63% is
high 90's cache hit rate of what was present.
Don't forget the way how old items are evicted from the
On Mon, May 27, 2024 at 02:38:08PM +0300, Michael Tokarev wrote:
> 27.05.2024 14:19, Thomas Huth wrote:
> > On 27/05/2024 12.49, Michael Tokarev wrote:
> > > Hi!
> > >
> > > Noticed today that a rebuild of basically the same tree (a few commits
> > > apart)
> > > in CI result in just 11% hit
On Mon, May 27, 2024 at 01:49:41PM +0300, Michael Tokarev wrote:
> Hi!
>
> Noticed today that a rebuild of basically the same tree (a few commits apart)
> in CI result in just 11% hit rate of ccache:
>
> https://gitlab.com/mjt0k/qemu/-/jobs/6947445337#L5054
>
> while it should be near 100%.
27.05.2024 14:19, Thomas Huth wrote:
On 27/05/2024 12.49, Michael Tokarev wrote:
Hi!
Noticed today that a rebuild of basically the same tree (a few commits apart)
in CI result in just 11% hit rate of ccache:
https://gitlab.com/mjt0k/qemu/-/jobs/6947445337#L5054
For me, the results look
On 27/05/2024 12.49, Michael Tokarev wrote:
Hi!
Noticed today that a rebuild of basically the same tree (a few commits apart)
in CI result in just 11% hit rate of ccache:
https://gitlab.com/mjt0k/qemu/-/jobs/6947445337#L5054
For me, the results look better:
Hi!
Noticed today that a rebuild of basically the same tree (a few commits apart)
in CI result in just 11% hit rate of ccache:
https://gitlab.com/mjt0k/qemu/-/jobs/6947445337#L5054
while it should be near 100%. What's interesting in there is:
1) cache size is close to max cache size,
and
