From: Zac Medico <zmedico@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Howto speed up compilations
Date: Mon, 18 Jul 2005 10:55:09 -0700 [thread overview]
Message-ID: <42DBECFD.5060506@gmail.com> (raw)
In-Reply-To: <20050718171913.GB5538@may.frognet.net>
John J. Foster wrote:
>
> OK, this happens all the time. I search, can't find what I want, post a
> question, search again, and there it is. This is not the "thread" I was
> talking about, but it was right in front of me on the Gentoo Wiki.
> http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs
>
> Does anyone have any "tips" on these "tips"?
>
I sincerely doubt that this technique is worth the trouble because the Linux virtual memory system will automatically cache frequently accessed files in ram. The tmpfs will eliminate filesystem overhead and will certainly result in a reduction of total build time. However, I'd go with Bruno's recommendation and just put -pipe in the cflags. For builds that work well in parallel, which most large builds do, distcc is a great way to speed things up.
Zac
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 18:05 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
2005-07-18 17:19 ` John J. Foster
2005-07-18 17:55 ` Zac Medico [this message]
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=42DBECFD.5060506@gmail.com \
--to=zmedico@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