From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Cero-state this week and last
Date: Sun, 8 Apr 2012 19:57:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1204081953081.31446@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw6Kz0Ma=+gaCq9TR6_VyH32t6GD_urhVQecVxX7U+U6Hg@mail.gmail.com>
On Sun, 8 Apr 2012, Dave Taht wrote:
> If I were to throw, say, a 48 cpu box at this problem, and do builds
> entirely out of ram (doable) I don't know how much further up a
> parallel build would scale. Certainly all the dependencies would have
> to get worked out.
>
> I sure wouldn't mind having a couple of these:
>
> http://www.penguincomputing.com/hardware/linux_servers/configurator/intel/relion2800
>
> or these:
>
> http://www.penguincomputing.com/hardware/linux_servers/configurator/amd/altus1804
>
> to play with.
>
> The ROI of stuff like that... vs the cost of electricity and rack
> space of the hardware we've had donated to this project - would
> probably pay off inside of a year or two, and that doesn't count the
> very real productivity improvement for everyone that could get a full
> build turned around in under 19 hours.
>
> Regrettably up-front capital like that is hard to come by, as
> bufferbloat.net is not an 'exciting new age startup' with billions of
> dollars per year of potential market cap. We're merely trying to save
> billions of people a lot of headache, frustration, and time, and get
> the technology into everything without any form of direct form of
> recompense. It's kind of a harder sell. For some reason.
>
> It's cheaper short term, if not long term, to bleed out electricity
> and rack space monthly, and try to have mental processes that cope
> with overnight builds, and scavange more free hardware wherever we
> can.
this sounds like the sort of thing that kickstarter (or similar) is
designed for.
you may also want to think about asking some of these companies for
donations directly.
> Incidentally I did cost out using amazon EC2, etc, last year, and that
> was highway robbery, given the amount of cpu cycles this task can
> consume.
yeah, I did some pricing on this sort of thing and found that if you
needed a system as much as 2 hours a day, you were better off just getting
a dedicated box from someplace like serverbeach.
David Lang
next prev parent reply other threads:[~2012-04-09 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 2:27 Dave Taht
2012-04-06 2:33 ` dpreed
2012-04-06 2:50 ` Dave Taht
2012-04-06 3:07 ` david
2012-04-08 15:53 ` Dave Taht
2012-04-09 2:57 ` david [this message]
2012-04-06 4:09 ` dpreed
2012-04-08 17:31 ` Dave Taht
2012-04-09 1:57 ` 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=alpine.DEB.2.02.1204081953081.31446@asgard.lang.hm \
--to=david@lang.hm \
--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