public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miguel S. Filipe" <m3thos@netcabo.pt>
To: "gentoo-dev@gentoo.org" <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Multiple emerges at the same time. ("multi-tasking" in portage)
Date: Thu, 06 Dec 2001 01:51:46 +0000	[thread overview]
Message-ID: <3C0ECF32.3090506@netcabo.pt> (raw)
In-Reply-To: 1007566748.1109.19.camel@zoidberg

While reading this,  It reminded me of a thought i allready had.

Why isn't portage more multi-task? What stops it from, while it's busy 
building something, downloading the packages that its going to 
(build/compile/install) next?
 This would speed up the merging process for those with slow internet 
connections, and it would not affect performance I believe. Is there any 
problem with this? Is it just dificult to implement, or its much more 
tricky and  problematic that it seems?

Mikael Hallendal wrote:

>tis 2001-12-04 klockan 14.54 skrev djamil essaissi:
>
>>la classe !
>>
>>portage question number N:
>>will it break anything emerging to independants packages (ebuilds) in
>>the same time ?
>>
>
>No, this is a very nice feature in Portage. Since it doesn't use a
>single shared database file it's no problem. You should look though that
>two seperate emergies doesn't try to install the packages (which might
>cause problems since the second might clean the build directory while
>the first one is working in there).
>
>Regards,
>  Mikael Hallendal
>
But.. in that case, I simply can't do.. since the second can mess up the 
first emerge. Right?

However, paralel emerges would be very nice, In fact.. another thing 
that crossed my mind.. is why doesn't portage,  builds independent 
packages in parallel(at the same time)?
  I'm saying this, because i've noticed in my SMP box, that, even when 
i'm "ebuilding" something, i still have a lot  of CPU idle.. (i used top 
to "check this out") it simply appears that, gcc, make and other apps 
don't take full use of the available CPU.

So, launching multiple ebuilds, and downloading, would use the system 
mutch more efficently, (and obviously, higher loads will make it more 
unsresponsive). There must be a way to take advange of this, without 
having the whole system at his knees (limiting the number of parallel 
ebuilds that would be launched automaticaly, but letting the user run 
has mutch has he pretends to).


Is this really a good idea? If not.. why?
Regards,

Miguel Sousa Filipe



  reply	other threads:[~2001-12-06  1:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 22:12 [gentoo-dev] Evolution 1.0 in Portage Mikael Hallendal
2001-12-04 13:54 ` djamil essaissi
2001-12-05 15:39   ` Mikael Hallendal
2001-12-06  1:51     ` Miguel S. Filipe [this message]
2001-12-06  6:04       ` [gentoo-dev] multitasked emerge (download while build ...) Mikael Hallendal
2001-12-06 10:15         ` djamil essaissi
2001-12-06 17:13           ` jano
2001-12-06 17:53             ` Daniel Robbins
2001-12-06  6:41       ` [gentoo-dev] Multiple emerges at the same time. ("multi-tasking" in portage) Daniel Robbins

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=3C0ECF32.3090506@netcabo.pt \
    --to=m3thos@netcabo.pt \
    --cc=gentoo-dev@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