Dne 02. 04. 23 v 15:22 Joe CHEN napsal(a):
Then koji is different, the chroot name will include a number, so
every task will cache from a new/empty directory.
---------------------------------------------------------------
http://miroslav.suchy.cz/blog/archives/2015/05/28/increase_mock_performan...
---------------------------------------------------------------
Building mock.src.rpm tasks 28 seconds!
That's very fast!
Can I ask the config of your VM?
Including "Hypervisor", "architecture", "virtual disk or
physical disk" "Cache mode"
or any specific config.
The setting in this blogpost was default settings of OpenStack. Nowdays we use various
backends, but all settings you
mentioned we keep on default - and disk is virtual, arch is x86_64.
My recommendation for tuning: start tuning just mock from command lines. Once you get it
to the level that is enough for
you (and you know that mock is capable of such speed), only then move to tuning how Koji
uses Mock. This way you will
have only one ball in the air - and not two at the same time.
Miroslav