From: Outback Dingo <outbackdingo@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] speeding up builds
Date: Sun, 29 Apr 2012 21:42:26 -0400 [thread overview]
Message-ID: <CAKYr3zw-Es=4MevUL9dOrhzuuzGApdHHj-ogzBpj_r03qzNn0A@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw51NC2y3_=ayM-RO0r4ErOUpgw8QM1DfuFunuWFC8pWvA@mail.gmail.com>
On Sun, Apr 29, 2012 at 8:15 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I finally acquired a machine with 32GB of ram, an intel 3930k (6
> cores), and an SSD.
>
> I put the build_dir, /tmp and /var/tmp on ramdisks, and...
>
> This cut a complete cerowrt build (including toolchain) down from >
> 3.5 hrs down to under 45 minutes.
>
> Without the toolchain rebuild, but after a make clean (to rebuild the
> packages and kernel), it's about 28 minutes.
>
> I can see that it is possible to parallelize things more to maybe chop
> another 30% of of things...
> ...but I'm glad to have 3 hrs of my life back, per build.
>
> I wanted to figure out to what extent modern hardware would enhance
> the existing buildbot system.
> Now I know...
odd my laptop will do a full build with tool chain in about an
hour..... its only a core i3 with 6gb and an ssd
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2012-04-30 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 0:15 Dave Taht
2012-04-30 1:42 ` Outback Dingo [this message]
2012-04-30 1:59 ` Dave Taht
2012-04-30 2:24 ` Dave Taht
2012-04-30 2:42 ` Dave Taht
2012-04-30 2:52 ` Dave Taht
2012-04-30 15:14 ` [Cerowrt-devel] Pointers on build setup? dpreed
2012-04-30 15:50 ` Dave Taht
2012-04-30 16:50 ` Dave Taht
2012-04-30 23:32 ` Maciej Soltysiak
2012-04-30 23:46 ` Dave Taht
2012-04-30 19:15 ` dpreed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKYr3zw-Es=4MevUL9dOrhzuuzGApdHHj-ogzBpj_r03qzNn0A@mail.gmail.com' \
--to=outbackdingo@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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