ccache stats and performance evaluation (in CI contexts)

Santiago Ruano Rincón via ccache <[email protected]> Wed, 8 Oct 2025 13:38:29 -0300
Newsgroups gmane.comp.compilers.ccache
Message-ID <aOaThXa1Dzz-GE9G@pokemon>
--===============7682525512189274023==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="kQxqDztYV34FOHbZ"
Content-Disposition: inline


--kQxqDztYV34FOHbZ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Joel and ccache developers team,

Thanks a lot for your useful project!

The debian's salsa CI project [salsaci] uses ccache as a way to reduce
building time, obviously in the CI build jobs. And I would like a to
ask you a question regarding how to handle the stats betweens job runs.

=46rom ccache(1) and the troubleshooting section, it is possible to read:

   Performance
       ...

       A good way of monitoring how well ccache works is to run ccache
       -s before and after your build and then compare the statistics
       counters. =E2=80=A6

Would you mind enlighten us about: is it a good idea to also reset/zero
the stats between two different jobs?

[salsaci] https://salsa.debian.org/salsa-ci-team/pipeline/

Thank you,

  -- Santiago

--kQxqDztYV34FOHbZ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQR+lHTq7mkJOyB6t2Un3j1FEEiG7wUCaOaTggAKCRAn3j1FEEiG
7//FAP4j4HB01YY5CooNXwgSFBYBVEP8wbcpL6/UTj6bSD1fNAD7BvTM6FdF4a3d
Nljm8cbi+eeMGI5sU9VH6dyE/F5MUgM=
=v6fy
-----END PGP SIGNATURE-----

--kQxqDztYV34FOHbZ--


--===============7682525512189274023==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ccache mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/ccache

--===============7682525512189274023==--