-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/18/2010 10:05 AM, Farkas Levente wrote: > On 01/18/2010 03:49 PM, Stephen Gallagher wrote: >> -----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 real bottleneck is not the rpmbuild itself (with ccache it cab be > very fast), but the mock surroundings. suppose there is build which > takes about 2 minutes and in mock it takes about 5 minutes:-( > most of the time is in yum, python tar, gzip etc which all use only one > cpu/core and it's very slow! > Well, if you know you're going to be running a number of builds inside the same chroot, you can do this: mock -r <fedora_version> --init mock -r <fedora_version> --chroot /path/to/chroot/above <package1> repeat as needed mock -r <fedora_version> --clean This way, you incur the heavy setup time only once for all packages. - -- 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/ iEYEARECAAYFAktUenUACgkQeiVVYja6o6MaWwCfV3WmVb43ZEbcf58wEleHtjQ7 CJgAn1n+ix+YHe4Lbf0w2nobbkmEdu1p =Qw25 -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
