On Mon, 18 Jan 2010, Farkas Levente wrote:
the real bottleneck is not the rpmbuild itself (with ccache it cab
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!
the tar and gzip are mostly BUILDING the cache.
Mock currently makes a cached copy of the buildroot it just created so it
doesn't have to redepsolve and download/install the rpms each time.
So the first time you run it makes a cache. You aren't clearing out the
cache each time, are you? That would definitely eat up a lot of time.