From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 8 cores
Date: Thu, 17 Jul 2008 03:18:01 -0700 [thread overview]
Message-ID: <1216289881.4327.59.camel@goose.sun.com> (raw)
In-Reply-To: <fde58473f8a89cc1e028b1ac3ab8c0c3@quanstro.net>
On Wed, 2008-07-16 at 22:09 -0400, erik quanstrom wrote:
> > On Tue, 2008-07-15 at 18:28 -0400, erik quanstrom wrote:
> >> coming as no suprise, the pc port of plan 9
> >> does work just fine with 8 cores.
> >>
> >> mpls; cat /dev/sysstat
> >> 0 14271 213501 3399 1116 0 0 0 99 0
> >
> > Looking at the output 99% is idle time. Have you had a chance to
> > look at this system when it is fully loaded with something
> > meaningful?
>
> not really. a kernel compile from ramfs took about 2.9s with an
> average of more than 3s of cpu used for every second of real time. a
> compile from the fs over a gigabit link took about 1s longer, but used
> far less cpu.
>
> neither is particular impressive, but i'm not using a great percentage
> of the cycles available ( ~3/8) and i am using the slowest processor on
> the sheet and, due to my misreading of the datasheet, i have only half
> the memory channels populated.
I see.
> did you have anything specific in mind?
Not really, no. Most of the benchmarks that I'm familiar with
would require a strong compiler support which is not (yet?)
available on Plan9. Things like SPEC OMP and the like. I was
looking more for a nice war story, I guess.
Thanks,
Roman.
next prev parent reply other threads:[~2008-07-17 10:18 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 22:28 erik quanstrom
2008-07-15 22:27 ` Benjamin Huntsman
2008-07-15 22:35 ` Williams, Mitch
2008-07-16 1:39 ` erik quanstrom
2008-07-16 5:12 ` Benjamin Huntsman
2008-07-16 7:00 ` sqweek
2008-07-16 12:54 ` Russ Cox
2008-07-16 11:37 ` C H Forsyth
2008-07-16 12:13 ` John Waters
2008-07-16 13:03 ` a
2008-07-16 13:44 ` Uriel
2008-07-16 13:55 ` John Waters
2008-07-16 14:16 ` Robert William Fuller
2008-07-16 13:07 ` erik quanstrom
2008-07-16 13:42 ` Uriel
2008-07-16 15:02 ` Benjamin Huntsman
2008-07-16 18:56 ` Uriel
2008-07-17 7:59 ` Kernel Panic
2008-07-17 9:07 ` Charles Forsyth
2008-07-17 10:04 ` Kernel Panic
2008-07-17 10:14 ` Roman V. Shaposhnik
2008-07-17 12:55 ` ron minnich
2008-07-17 12:58 ` William Josephson
2008-07-17 13:45 ` erik quanstrom
2008-07-17 14:11 ` ron minnich
2008-07-17 14:32 ` Roman V. Shaposhnik
2008-07-17 13:32 ` Paweł Lasek
2008-07-17 14:07 ` Kernel Panic
2008-07-16 22:44 ` Iruata Souza
2008-07-17 8:38 ` Kernel Panic
2008-07-17 18:14 ` Iruata Souza
2008-07-23 11:42 ` matt
2008-07-23 18:32 ` Iruata Souza
2008-07-16 1:41 ` andrey mirtchovski
2008-07-16 20:38 ` Roman V. Shaposhnik
2008-07-17 2:09 ` erik quanstrom
2008-07-17 10:18 ` Roman V. Shaposhnik [this message]
2008-07-17 12:41 erik quanstrom
2008-07-17 12:56 ` William Josephson
2008-07-17 12:58 ` ron minnich
2008-07-17 13:46 ` erik quanstrom
2008-07-17 14:06 ` 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=1216289881.4327.59.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).