public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Simultaneously emerging multiple packages with same dependencies
Date: Thu, 27 Jan 2011 23:18:22 +0100	[thread overview]
Message-ID: <201101272318.23087.joost@antarean.org> (raw)
In-Reply-To: <AANLkTi=NUs0nSi9uR9KkMeQ60BXANywUfLDnZu_Vp2WC@mail.gmail.com>

On Thursday 27 January 2011 23:05:22 Paul Hartman wrote:
> On Thu, Jan 27, 2011 at 3:46 PM, J. Roeleveld <joost@antarean.org> wrote:
> > On Thursday 27 January 2011 21:25:02 Paul Hartman wrote:
> >> On Thu, Jan 27, 2011 at 2:15 PM, Nikos Chantziaras <realnc@arcor.de> 
wrote:
> >> > On 01/27/2011 09:41 PM, Dale wrote:
> >> >> YoYo Siska wrote:
> >> >>> Yes.
> >> >>> It might not be perfect, but mostly it works pretty well.
> >> >>> Once make started 10 or so process, which ate all my ram, because I
> >> >>> forgot to reenable swap, when I was playing with something before
> >> >>> that
> >> >>> 
> >> >>> :)
> >> >>> 
> >> >>> yoyo
> >> >> 
> >> >> I noticed the same thing with mine. It used a LOT of ram. I have 4Gbs
> >> >> and it was up to about 3Gbs at one point and using some swap as well.
> >> >> I'm hoping to max out to 16Gbs as soon as I can. May upgrade to a 6
> >> >> core CPU too.
> >> >> 
> >> >> I wonder how much faster it would be if the work directory is put on
> >> >> tmpfs? With 16Gbs, that should work even for OOo.
> >> > 
> >> > Btw, if you're using more instances than the amount of CPUs, the
> >> > result will be slow-down.
> >> > 
> >> > With the default kernel scheduler, best if amount of CPUs + 1.  (On a
> >> > 4-core, that's -j5).
> >> 
> >> Once, when building my kernel, I accidentally forgot to specify the
> >> number of makes and ran "make -j all". That was a really bad idea, the
> >> system became totally unresponsive for quite a long time, much longer
> >> than normal kernel build time, but it did eventually finish!
> > 
> > I have found that multi-core systems with sufficient memory can handle
> > "-j" (no value) a lot better then sindle-core systems. I do on occasion
> > do it with the kernel and can still continue using the system. (For
> > comparison, my desktop is a 4-core AMD64 with 8GB memory)
> 
> Strange, in my case it was an i7 920 (4 cores, hyperthreaded, appears
> as 8 CPUs to Linux) with 12GB of RAM. Maybe if I prefixed it
> with"nice" it would not have brought my computer to its knees... or
> maybe related to the schedulers and other kernel voodoo that I don't
> understand. I might try it again someday :)

That is strange, unless your harddrive is really underperforming?
Or do you have all the options in the kernel selected?

Btw, HyperThreading doesn't work too well when you have a lot of identical 
tasks. In that case, you might end up with lesser performance as there are no 
"usable unused" parts in your cores, but the CPU-schedules (the hardware one 
for HT) is looking for things to fill those last few bits with.

--
Joost



  reply	other threads:[~2011-01-27 22:20 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 [this message]
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
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=201101272318.23087.joost@antarean.org \
    --to=joost@antarean.org \
    --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