public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] {OT} Need a new server
Date: Fri, 13 Sep 2013 13:00:09 -0700	[thread overview]
Message-ID: <CAN0CFw0dkS=vCSXTPWyXDKOi=RVzKGEqXo56YiupvejfvJc1yQ@mail.gmail.com> (raw)

It's time to switch hosts.  I'm looking at the following:

Dual Xeon E5-2690
32GB RAM
4x SSD RAID10

This would be my first experience with multiple CPUs and RAID.  Advice
on any of the following would be greatly appreciated.

Are there any administrative variations for a dual-CPU system or do I
just need to make sure I enable the right kernel option(s)?

Is the Gentoo Software RAID + LVM guide the best place for RAID
install info if I'm not using LVM and I'll have a hardware RAID
controller?

http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml

Since RAM is so nice for buffers/cache, how do I know when to stop
adding it to my server?

Can I count on this system to keep running if I lose an SSD?

Is a 100M uplink enough if this is my only system on the LAN?

Is hyperthreading worthwhile?

Any opinions on Soft Layer?

- Grant


             reply	other threads:[~2013-09-13 20:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 20:00 Grant [this message]
2013-09-13 20:39 ` [gentoo-user] {OT} Need a new server Alan McKinnon
2013-09-13 21:39   ` Grant
2013-09-14  8:14     ` Alan McKinnon
2013-09-14  8:54       ` Grant
2013-09-14  9:02         ` Alan McKinnon
2013-09-14  9:14           ` Grant
2013-09-13 20:44 ` Michael Orlitzky
2013-09-13 21:47   ` Grant
2013-09-13 22:47     ` Peter Humphrey
2013-09-13 22:54       ` Daniel Frey
2013-09-14  8:50         ` Grant
2013-09-14 11:32           ` Tanstaafl
2013-09-15 11:15             ` Grant
2013-09-16  9:54               ` Tanstaafl
2013-09-14 14:37           ` Michael Orlitzky
2013-09-16  6:49             ` Grant
2013-09-16 13:10               ` Michael Orlitzky
2013-09-17  6:43                 ` Grant
2013-09-17 12:30                   ` Michael Orlitzky
2013-09-17 13:13                     ` Grant
2013-09-17 16:46                       ` Alan McKinnon
2013-09-13 23:17     ` Michael Orlitzky
2013-09-14  8:52       ` Grant
2013-09-14 11:35     ` Tanstaafl
2013-09-13 21:58 ` thegeezer
2013-09-13 22:14   ` Grant
2013-09-14  8:59 ` [gentoo-user] " Grant
2013-09-14  9:10   ` Alan McKinnon
2013-09-14  9:29     ` Grant
2013-09-14 11:07       ` Michael Hampicke
2013-09-15 11:07         ` Grant
2013-09-14 14:36       ` Alan McKinnon
2013-09-14 11:34     ` Tanstaafl
2013-09-14 14:42       ` Alan McKinnon
2013-09-14 11:04   ` thegeezer
2013-09-15 11:05     ` Grant
2013-09-14 11:18 ` [gentoo-user] " Tanstaafl
2013-09-15 11:10   ` Grant
2013-09-17  5:36     ` Pandu Poluan
2013-09-17  6:32       ` Grant
2013-09-17  9:24       ` Neil Bothwick
2013-09-17 10:01       ` Tanstaafl
2013-09-17  7:28   ` Grant
2013-09-17  7:37     ` Pandu Poluan
2013-09-17  9:49       ` Grant
2013-09-17 10:10         ` Alan McKinnon
2013-09-17 13:11           ` Grant
2013-09-17 16:49             ` Alan McKinnon

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='CAN0CFw0dkS=vCSXTPWyXDKOi=RVzKGEqXo56YiupvejfvJc1yQ@mail.gmail.com' \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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