public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Simultaneously emerging multiple packages with same dependencies
Date: Thu, 27 Jan 2011 15:36:37 +0000	[thread overview]
Message-ID: <20110127153637.0ea4101a@digimed.co.uk> (raw)
In-Reply-To: <ihs1qu$pl6$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Thu, 27 Jan 2011 17:09:27 +0200, Nikos Chantziaras wrote:

> > So on a 20 package world update, only 19 are faster while the 20th
> > runs at the same speed? Where's the loss there? Even if the last were
> > slower, it would be worth it.  
> 
> Given the amount of time unpack/configure/install of most packages
> needs (very short), my observation is that it would not be worth it.

Even if that were true, how much time would you have to save to justify
adding -j 2 to EMERGE_DEFAULTS in make.conf?

But it's not true, large packages spend a lot of time on these phases of
the install.


-- 
Neil Bothwick

Head: (n.) the part of a disk drive which detects sectors and decides
which of the two possible values to return: 'lose a turn' or 'bankrupt.'

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2011-01-27 15:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 12:12 [gentoo-user] Simultaneously emerging multiple packages with same dependencies PK
2011-01-26 13:07 ` Petri Rosenström
2011-01-26 13:49 ` Neil Bothwick
2011-01-26 18:28   ` PK
2011-01-26 19:43     ` Jacob Todd
2011-01-27  5:12 ` [gentoo-user] " Nikos Chantziaras
2011-01-27 10:01   ` Neil Bothwick
2011-01-27 13:11     ` Dale
2011-01-27 13:33       ` Nikos Chantziaras
2011-01-27 14:05         ` YoYo Siska
2011-01-27 14:12           ` J. Roeleveld
2011-01-27 18:13             ` YoYo Siska
2011-01-27 19:41               ` Dale
2011-01-27 20:15                 ` Nikos Chantziaras
2011-01-27 20:25                   ` Paul Hartman
2011-01-27 21:46                     ` J. Roeleveld
2011-01-27 22:05                       ` Paul Hartman
2011-01-27 22:18                         ` J. Roeleveld
2011-01-27 22:59                           ` Mick
2011-01-28  7:16                             ` J. Roeleveld
2011-01-27 21:11                   ` Bill Longman
2011-01-27 22:53                   ` Dale
2011-01-28  7:16                     ` J. Roeleveld
2011-01-28 14:53                       ` Dale
2011-01-27 14:16         ` Neil Bothwick
2011-01-27 14:30           ` Nikos Chantziaras
2011-01-27 14:53             ` Neil Bothwick
2011-01-27 15:09               ` Nikos Chantziaras
2011-01-27 15:15                 ` Alan McKinnon
2011-01-27 15:43                   ` Dale
2011-01-27 15:36                 ` Neil Bothwick [this message]
2011-01-27 18:56                   ` Allan Gottlieb
2011-01-27 19:18                     ` J. Roeleveld
2011-01-27 21:06                       ` YoYo Siska
2011-01-27 22:02                         ` J. Roeleveld
2011-01-27 22:14                         ` J. Roeleveld
2011-02-04 22:06                     ` Enrico Weigelt
2011-01-27 15:14         ` Paul Hartman
2011-02-04 21:14       ` Enrico Weigelt
2011-01-27 15:33   ` PK
     [not found] <gfdih-76I-1@gated-at.bofh.it>
     [not found] ` <gfsr0-7M6-1@gated-at.bofh.it>
     [not found]   ` <gfwXE-72T-3@gated-at.bofh.it>
2011-01-27 16:04     ` David W Noon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110127153637.0ea4101a@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox