On Mon, Jan 18, 2010 at 17:30, Ville Skyttä ville.sky...@iki.fi wrote:
On Monday 18 January 2010, Seth Vidal wrote:
On Mon, 18 Jan 2010, Farkas Levente wrote:
the real bottleneck is not the rpmbuild itself (with ccache it cab be
very fast), but the mock surroundings. suppose there is build
Le 03/04/2011 12:31, Farkas Levente a écrit :
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:-(
I use for a while a full /dev/shm mock
Am 03.04.11 13:17, schrieb Remi Collet:
Le 03/04/2011 12:31, Farkas Levente a écrit :
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:-(
I
On 01/18/2010 04:10 PM, Seth Vidal wrote:
On Mon, 18 Jan 2010, Farkas Levente wrote:
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
On Mon, 18 Jan 2010, Farkas Levente wrote:
the tar and gzip are mostly BUILDING the cache.
no tar and gzip used unpacking root cache.
How slow are your disks? You're not doing any of this to nfs are you?
but have to run yum each time for the package specific depsolve and yum
Farkas,
Don't email just to me offlist. Keep this onlist.
How much of this is network access and how much is disk? B/c I doubt
very much that you're cpu bound at all.
everything is on the local mirror server which is on a gigabit lan. is there
any way to banchmark mock and different
On Monday 18 January 2010, Seth Vidal wrote:
On Mon, 18 Jan 2010, Farkas Levente wrote:
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:-(
On 10-01-18 11:34:44, Ville Skyttä wrote:
...
So instead of modifying specfiles, one can do something like this in
/etc/mock/site-defaults.cfg:
config_opts['macros']['%_smp_mflags'] = '-j3'
Unless `rpmbuild --showrc` shows a bad definition for _smp_mflags,
you're probably better off
On Monday 18 January 2010, Tony Nelson wrote:
On 10-01-18 11:34:44, Ville Skyttä wrote:
...
So instead of modifying specfiles, one can do something like this in
/etc/mock/site-defaults.cfg:
config_opts['macros']['%_smp_mflags'] = '-j3'
Unless `rpmbuild --showrc` shows a bad
On Mon, 2010-01-18 at 10:10 -0500, Seth Vidal wrote:
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.
Or running builds a long time apart, as the cache gets aged out. On my
system (an overclocked
On Mon, 2010-01-18 at 15:30 -0500, Tony Nelson wrote:
On 10-01-18 11:34:44, Ville Skyttä wrote:
...
So instead of modifying specfiles, one can do something like this in
/etc/mock/site-defaults.cfg:
config_opts['macros']['%_smp_mflags'] = '-j3'
Unless `rpmbuild --showrc` shows a bad
11 matches
Mail list logo
