public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel da Veiga <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Howto speed up compilations
Date: Mon, 18 Jul 2005 16:01:32 -0300	[thread overview]
Message-ID: <342e1090507181201178ea14a@mail.gmail.com> (raw)
In-Reply-To: <42DBF792.40107@gmail.com>

That sounded nice, if you can come with a "cluster" for compilation
you may see good results, I've never used distcc but a friend got
three athlon xps running and did it, he was able to install the three
gentoos within a day (wich is more than I could ever expect after my 2
days stage1 install with no x or openoffice).

On 7/18/05, Colin <signofzeta@gmail.com> wrote:
> Neil Bothwick wrote:
> 
> >On Mon, 18 Jul 2005 14:14:41 -0300, Bruno Lustosa wrote:
> >
> >
> >
> >>>A few weeks ago I read in one of the newgroups a way to greatly
> >>>decrease compilation times. The author noted that this was
> >>>particularly noticable when working with something like OO. The
> >>>general jist of it was to create temporary file system in memory and
> >>>mount your portage tmpdir there. For the life of me, I can't find
> >>>that thread anymore. Does anyone do something similar to this? Are
> >>>there noticable gains to be had. I have an Athlon 2800XP and 1 GB ram.
> >>>
> >>>
> >>I am not sure if this will give a tremendous speedup. Granted, the
> >>source files won't need to be read from disk, which is an advantage,
> >>however, the file reading time should be very small compared to the
> >>time it takes for the compiler to translate the source code into
> >>machine code.
> >>Also, there's the ammount of memory you will lose, memory that could
> >>be used by the compiler. In some cases, gcc can eat very big chunks of
> >>memory.
> >>
> >>
> >
> >Not to mention the OOo ebuild needing around 3GB of space in TMPDIR, so
> >this approach would only result in the emerge failing quicker.
> >
> >
> Not if you've got a machine with more than 3 GB of memory.  A dual-proc
> Power Mac G5 can handle up to 8 GB of physical RAM.  If you did this
> trick on one of those, you might see some serious improvement!  But with
> most PC's being limited (by the x86 and motherboard designs) to 2 GB of
> physical RAM, it wouldn't work with large apps.
> 
> A good suggestion would be to grab some old computers, Gentoo-ize them,
> network them over 100BaseTX or Gigabit and make a little distcc farm.
> Plus, you can charge people if they want to come over and rent your
> computing power.  (Virginia Tech does that with their "System X," 1,100
> dual-2.3GHz-processor XServe G5's.)  :-)
> --
> Colin
> --
> gentoo-user@gentoo.org mailing list
> 
> 


-- 
Daniel da Veiga
Computer Operator - RS - Brazil

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-07-18 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 17:07 [gentoo-user] Howto speed up compilations John J. Foster
2005-07-18 17:14 ` Bruno Lustosa
2005-07-18 17:55   ` Neil Bothwick
2005-07-18 18:40     ` Colin
2005-07-18 18:55       ` John J. Foster
2005-07-18 19:01       ` Daniel da Veiga [this message]
2005-07-18 17:19 ` John J. Foster
2005-07-18 17:55   ` Zac Medico
2005-07-18 19:06     ` Richard Fish
2005-07-18 17:23 ` David Morgan
2005-07-18 17:26 ` [gentoo-user] " Francesco Talamona
2005-07-18 21:39   ` Nick Rout
2005-07-19 10:03 ` [gentoo-user] " Rafer
2005-07-19 21:11   ` Zac Medico

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=342e1090507181201178ea14a@mail.gmail.com \
    --to=danieldaveiga@gmail.com \
    --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