From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] some #s
Date: Tue, 3 Jun 2003 22:21:32 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0306032215140.6478-100000@maxroach.lanl.gov> (raw)
The geode cluster Andrey mentioned has a clone that etherboots linux and
comes up running bproc etc. (see clustermatic.org for info on this). The
two clusters are identical in every way.
Time from power-on to full cluster ready to roll (i.e ready for bproc
equivalent of 'cpu'): 10 seconds
Some timing for same hardware with 9load/plan 9:
0->10 seconds: 9load is up and has loaded the plan 9 kernel over ether
10-20 seconds: no real output from plan 9
20-30 seconds (or so): until I get the 'boot from [il]' prompt
Obviously we'll try to speed this up just a bit, but still, it's not too
terrible. I need to get it to skip the prompt step but that doesn't seem
like a big deal (there is no console, really, on these machines, so a
prompt is rather unimportant, esp. given there is only one choice)
Overall there's lots more procs needed to make the plan 9 nodes work as
cluster nodes than the Linux bproc stuff -- about a factor of 5. bproc
does remote exec somewhat faster, I'm working on the #s there too. But
plan 9 does do some thing better than bproc. So it's a bit of a wash in
most ways. Nevertheless I'm going to see what else I can eliminate.
Anyway, this is just FYI, I'm hoping to get good ideas from people at
usenix on reducing some overheads on this system.
ron
next reply other threads:[~2003-06-04 4:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 4:21 ron minnich [this message]
2003-06-04 4:45 ` andrey mirtchovski
2003-06-04 14:31 ` ron minnich
2003-06-04 11:27 ` C H Forsyth
2003-06-04 14:39 ` ron minnich
2003-06-04 15:39 ` andrey mirtchovski
2003-06-04 21:20 ` northern snowfall
2003-06-04 23:06 ` [9fans] " Jim Choate
2003-06-05 0:24 ` northern snowfall
2003-06-05 3:20 ` Dan Cross
2003-06-05 11:33 ` Jim Choate
2003-06-05 22:41 ` Dan Cross
2003-06-05 23:06 ` Jim Choate
2003-06-06 0:25 ` David Presotto
2003-06-06 1:08 ` Dan Cross
2003-06-06 1:19 ` David Presotto
2003-06-06 3:58 ` northern snowfall
2003-06-06 3:41 ` ron minnich
2003-06-06 11:36 ` Jim Choate
2003-06-06 4:04 ` northern snowfall
2003-06-06 12:01 ` Jim Choate
2003-06-06 12:02 ` David Presotto
2003-06-06 1:21 ` boyd, rounin
2003-06-06 2:24 ` Russ Cox
2003-06-06 3:15 ` Dan Cross
2003-06-06 4:17 ` northern snowfall
2003-06-06 3:33 ` Dan Cross
2003-06-06 4:45 ` northern snowfall
2003-06-06 5:46 ` Dan Cross
2003-06-06 9:48 ` northern snowfall
2003-06-06 3:51 ` boyd, rounin
2003-06-06 15:45 ` Jack Johnson
2003-06-05 3:20 ` [9fans] " ron minnich
2003-06-04 16:46 ` jmk
2003-06-04 22:38 ` 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=Pine.LNX.4.44.0306032215140.6478-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).