From: Francesco Riosa <vivo75@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Six month major project on Gentoo
Date: Thu, 22 Dec 2011 12:11:32 +0100 [thread overview]
Message-ID: <CAD6zcDwnexHze1S0uAnBCxVV6quh_JvU+pRAvtxefagyUHzKnQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_==iegE4yhtsG4Rn=ZefHeTQduwtt6pSnb5HbaRZTgU9g@mail.gmail.com>
2011/12/22 Rich Freeman <rich0@gentoo.org>:
> On Wed, Dec 21, 2011 at 11:43 PM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
>> I looked into this 6 or 7 years ago. It wasn't feasible unless you were
>> on an extremely high-speed, low-latency network, beyond what was
>> typically accessible at the time outside of universities and LANs. Could
>> be worth exploring again now that 25-100 mbps connections are becoming
>> more common.
>
> I tried messing around with this with Amazon EC2. The problem was
> that due to latency I only really saw the benefit for VERY high levels
> of parallelization (think -j25+).. However, make isn't actually
> "distcc-aware" so it just runs 25 jobs of anything in parallel. So,
> anytime a makefile launched a ton of java or python jobs the host
> ground to a halt as it wasn't distributed and it was way more than the
> host could handle (especially java - which swapped like there was no
> tomorrow).
>
> If somebody were to do a distcc-ng for a large cluster one of the
> problems to solve would be having it not run jobs in parallel if it
> couldn't actually distribute them.
>
> Rich
>
Just wanted to point out that (if there is enough memory) recent
kernels manage much better parallelism, even excess of it, once
reached the maximum load augmenting threads only bring minimal loss of
"real" time.
next prev parent reply other threads:[~2011-12-22 11:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 11:06 [gentoo-dev] Six month major project on Gentoo Gaurav Saxena
2011-12-14 18:05 ` Christian Ruppert
2011-12-14 18:14 ` "C. Bergström"
2011-12-15 18:07 ` Gaurav Saxena
2011-12-19 17:46 ` Christian Ruppert
2011-12-14 18:29 ` Alec Warner
2011-12-15 18:09 ` Gaurav Saxena
2011-12-22 4:43 ` Donnie Berkholz
2011-12-22 10:52 ` Rich Freeman
2011-12-22 11:11 ` Francesco Riosa [this message]
2011-12-22 15:55 ` Michał Górny
2011-12-22 16:09 ` Rich Freeman
2011-12-22 17:40 ` [gentoo-dev] " Duncan
2011-12-18 17:02 ` [gentoo-dev] " Petteri Räty
2011-12-18 17:13 ` "Paweł Hajdan, Jr."
2011-12-18 17:17 ` [gentoo-dev] libbash licensing Petteri Räty
2011-12-18 17:45 ` [gentoo-dev] Six month major project on Gentoo Michał Górny
2011-12-19 18:14 ` Sébastien Fabbro
2012-01-02 14:33 ` "Paweł Hajdan, Jr."
[not found] <i7USJ-40Q-3@gated-at.bofh.it>
2011-12-14 21:25 ` Leho Kraav
2011-12-14 23:43 ` Alec Warner
2011-12-14 23:58 ` Mike Frysinger
2011-12-15 5:39 ` Nirbheek Chauhan
2011-12-15 12:27 ` Mike Frysinger
2011-12-15 12:42 ` Nirbheek Chauhan
2011-12-15 12:43 ` Rich Freeman
2011-12-15 16:30 ` Mike Frysinger
2011-12-15 16:51 ` Mike Frysinger
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=CAD6zcDwnexHze1S0uAnBCxVV6quh_JvU+pRAvtxefagyUHzKnQ@mail.gmail.com \
--to=vivo75@gmail.com \
--cc=gentoo-dev@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