Am 12.02.24 um 22:10 schrieb Miroslav Suchý:
Dne 12. 02. 24 v 19:29 Julian Sikorski napsal(a):
Hello,
has anyone successfully managed to get ccache to speed up kernel
mockbuilds, be it SRPMS from kernel-ark or from dist-git? I gave it a
brief shot but saw no difference, if anything the build was slower.
The machine I am building on has 32 GB RAM which is not quite enough
to fit everything on a ramdisk, and the drive I am building to is an
NVME SSD, "only" PCI Express 3.0. CPU is a Ryzen 5 5600x. A baseonly
builds takes about 25 minutes, which is somewhat annoying when one has
to bisect something.
If ccache can speed this up, how big does it need to be? I understand
the default 4 GB is nowhere near enough but what would be needed to
actually help? Thanks!
Just to be sure - did you configured Mock to use it?
https://rpm-software-management.github.io/mock/Plugin-CCache
the build from build container cannot see host ccache, so Mock must
specially configure it.
This is by default off, because in multi user environment you can easily
poison the cache and affect different build. This should be enabled only
on VM where you trust all users that can run Mock. E.g. your personal
developer workstation.
I am building with:
--enable-plugin=ccache --plugin-option=ccache:max_cache_size='40G'
Building with cold cache took 29:29, building with hot cache 29:45, so
there appears to be no benefit so far.
/var/cache/mock/fedora-36-x86_64/ccache is 9,5G in size, suggesting that
size is not the problem.
I am down to 21 commits to bisect after the current one, so changes to
kernel source tree should be minimal at this point.
Do I need to install ccache on the host as well?
Best regards,
Julian
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
