how to speed up mock?

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/18/2010 09:38 AM, Farkas Levente wrote:
> hi,
> we use mock for local package build, but it's very slow. now we install 
> a new host just for mock with 8core, ram disks etc. it seems it still 
> slow. first of all most of the time mock use only one 1 core of the cpu. 
> is there any way to speed up different part of the mock build process?
> thanks in advance.
> 
> ps. anyway is there any better place to discuss it?
> 


Mock itself is pretty fast, and when it's doing source compilations, it
will automatically use as many CPUs as you have available.

The bottleneck, however, is in autoconf. When building a package, in
many cases the lion's share of the build time goes to running through
autoconf, which cannot run in parallel (to my knowledge) and uses a
great deal of disk I/O.

However, one trick you might consider doing is adding in a --cache-file
argument to the call to %configure in your makefiles. This will store a
copy of the configure results on-disk in a location of your choosing.
Builds after the initial creation of this file will refer to it for
answers and will run much faster.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAktUdREACgkQeiVVYja6o6PL7gCgpGPzl603zLEUQF8rjbQlQfTZ
yqwAn15XzeVk4aZAoKwTPhZLiWCE+771
=C8bH
-----END PGP SIGNATURE-----