9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 8 cores
Date: Wed, 16 Jul 2008 09:07:07 -0400	[thread overview]
Message-ID: <04f144fe676d955cc6752031049705a9@quanstro.net> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB2EE@dolly.ntdom.cupdx>

> I'd like to ask a question, but before I do, feel I should say, I've
> been on this list long enough to understand that Plan 9 is a research
> vessel, not an OS that's targeted at commercial deployment...

i can't agree with this label "research os" if you mean
to imply that it's not stable or somehow unfinished.

i run the company's infastructure on plan 9 and our main product
— that is my paycheck — depends on plan 9.

i spend a lot less time fixing things now than i did when i
ran a different company's infastructure on aix and linux.
i also suffer much less downtime.

on the other hand, if by "research os" you mean simple
and flexable, then i couldn't agree more.

> That being said, while huge scalability is certainly research-worthy,
> does anyone actually run anything on Plan 9 that needs or would
> otherwise benefit from 8+ CPUs and more than a few GB's of RAM?

this style product will easily scale to that level

	http://tinyurl.com/5e3q9p	[coraid.com]

the real question is can you find a big enough
chassis.

if that doesn't compel you, running upas imap server for ~40 users
with 1.3gb of inboxes might.  since upas has the bad manners to load
the entire mailbox, we're using about 90% of the 3.5gb bios will spare
us in 32bit mode.  i also watched it at 100% cpu for a solid hour
yesterday.

it's embarassing that mail is such a hog.  this is our scalability plan:

	/n/sources/contrib/quanstro/src/nupas/

- erik




  parent reply	other threads:[~2008-07-16 13:07 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 [this message]
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
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=04f144fe676d955cc6752031049705a9@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).