9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: balaji <balaji.srinivasa+plan9@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] higher-end compute server recommendations?
Date: Wed, 25 Jul 2012 09:44:31 -0700	[thread overview]
Message-ID: <CANE8QwdU0dYvJVhMQL5UWWawVP1To2iEwprdQspz4Mtyuoaa3g@mail.gmail.com> (raw)
In-Reply-To: <da97f85b72e32f832d1314272e7f1e89@kw.quanstro.net>

unlike newegg, acmemicro does not stock anything so delivery time is long.

On Tue, Jul 24, 2012 at 9:58 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Wed Jul 25 00:45:01 EDT 2012, john@jfloren.net wrote:
>> We've got some budget left for hardware, so I'm looking for a server
>> suitable for running Plan 9, preferably as good as I can get for about
>> $3000-5000. Buying non-Thinkpad Plan 9 hardware is kind of a
>> crapshoot, and this isn't just some $100 Atom system, so if any of you
>> are running something along these lines, please let me know. I'd most
>> like to see lots of cores and lots of RAM, I don't even want storage
>> (we've got other methods for storage).
>
> hey, john, i've had incredible luck with intel servers from supermicro
> for general beat-about servers.
>
> just as a quick suggestion, i'd look at this server here.
>
> http://www.supermicro.com/products/system/1U/6017/SYS-6017R-WRF.cfm
>
> with 8-core socket-r cpus, you can have 32 cores and 128gb of memory
> without stretching the budget too much.  the intel i350 nics work fine,
> but for something that hot, i'd get a myircom or intel 10gbe adapter.
>
> this was just whatever came up in 5 minutes.  you might want to look
> at this page here for more options
>
> http://www.supermicro.com/products/nfo/Xeon_X9_E5.cfm?pg=SS
>
> acmemicro.com (fitting, no?) should have the full range of stuff.
>
> - erik
>



  parent reply	other threads:[~2012-07-25 16:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL4LZyhmurX-fykvMi-yzQu3vNsNCM1AAWwMw=bu+Sd_3cQ3rA@mail.gmail.c>
2012-07-25  4:58 ` erik quanstrom
2012-07-25  5:09   ` John Floren
2012-07-25  5:28     ` Bruce Ellis
2012-07-25 16:44   ` balaji [this message]
2012-07-25 16:53     ` Kurt H Maier
     [not found]   ` <CANE8QwdU0dYvJVhMQL5UWWawVP1To2iEwprdQspz4Mtyuoaa3g@mail.gmail.c>
2012-07-25 16:47     ` erik quanstrom
2012-07-25 16:56       ` balaji
2012-07-25 20:16         ` hiro
     [not found]         ` <CAFSF3XOMFKiZ4-KniUHMVxbAzoQbFp=mCfUO=mquAffcMA_1+w@mail.gmail.c>
2012-07-25 20:38           ` erik quanstrom
2012-07-25 20:58             ` hiro
2012-07-25 21:38               ` cinap_lenrek
2012-07-26  7:33   ` Richard Miller
2012-07-26 12:20     ` Oleksandr Iakovliev
2012-07-26 12:40       ` Richard Miller
2012-07-26 14:10         ` erik quanstrom
2012-07-26 14:26           ` David Leimbach
2012-07-26 15:16             ` andrey mirtchovski
2012-07-26 20:28               ` David Leimbach
     [not found]             ` <CAK4xykXEx8p8bHMf0oorriCunm-1gzkB=Vn7kRvDBZeL4uF82A@mail.gmail.c>
2012-07-26 17:04               ` erik quanstrom
2012-07-26 17:57                 ` tlaronde
2012-07-26 20:29                   ` David Leimbach
2012-07-25  4:43 John Floren

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=CANE8QwdU0dYvJVhMQL5UWWawVP1To2iEwprdQspz4Mtyuoaa3g@mail.gmail.com \
    --to=balaji.srinivasa+plan9@gmail.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).