From: "Wes Kussmaul" <wes@village.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] cluster in sigle case
Date: Fri, 3 Sep 2004 09:46:39 -0400 [thread overview]
Message-ID: <0b3201c491bc$7563a400$6501a8c0@dell8100> (raw)
In-Reply-To: <20040903145222.3f9a582a@garlic.apnic.net>
> 1500watts at the wallplug is going to make a hot cable. I've met domestic
> wiring which shat itself on a 3 bar heater..
That's 1500W for the 96 processor machine. If you're going to make a
commitment to acquire that much processing power, surely you can make a
commitment to installing a 30 amp circuit. If it's in a house, use one phase
of an electric dryer circuit (and try to remember not to run the dryer and
the computer at the same time.)
next prev parent reply other threads:[~2004-09-03 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 22:38 alexandr
2004-09-03 4:27 ` Sam
2004-09-03 4:02 ` Tim Newsham
2004-09-03 4:52 ` George Michaelson
2004-09-03 13:46 ` Wes Kussmaul [this message]
2004-09-03 5:09 ` andrey mirtchovski
2004-09-03 14:10 ` ron minnich
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='0b3201c491bc$7563a400$6501a8c0@dell8100' \
--to=wes@village.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).