From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Rafa Griman <rafagriman@gmail.com>
Subject: Re: [gentoo-user] Dual or Quad CPU complications?
Date: Sat, 15 Dec 2012 18:49:30 +0100 [thread overview]
Message-ID: <1832535.yE7Zi1bxev@localhost> (raw)
In-Reply-To: <CANRt_=aSJyQLNU6A_Sjtm6yAZiUddmfkcWYTCjN17Jn_tEdLfA@mail.gmail.com>
Am Freitag, 14. Dezember 2012, 08:55:08 schrieb Rafa Griman:
> On Thu, Dec 13, 2012 at 7:22 PM, Volker Armin Hemmann
>
> <volkerarmin@googlemail.com> wrote:
> > Am Mittwoch, 12. Dezember 2012, 22:12:18 schrieb Grant:
> >> I've only ever used systems with a single CPU. I'm looking for a new
> >> host
> >> for a dedicated server (suggestions?) and it looks like I'll probably
> >> choose a machine with two or four CPUs. What sort of complications does
> >> that add to set up and/or maintenance with Gentoo?
> >
> > none
> >
> > also, forget numa. You won't deal with douzends of cores each using local
> > memory and acccession the memory managed by the other cores.
>
> It depends on his application, maybe his application does benefit on
> NUMA architecture. Until we don't know what he's running, we can't
> really say this or that architecture/technology is of no use ;)
>
> So Volker, what applications are you running (and BTW: what volume of
> data are you managing, how many users, ...)? This will helps us help
> you :)
you don't get NUMA just for free.
You have to buy NUMA hardware. If the hardware you buys does not scream NUMA
at you, you don't have it. It is really that simple.
Multicore, multisocket systems MIGHT be NUMA systems - but that is not a
guarantee. Now can this stupid thread please die away?
There are no caveats going from single to multicore on consumer hardware. and
even on non consumer hardware there aren't many.
--
#163933
next prev parent reply other threads:[~2012-12-15 17:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 6:12 [gentoo-user] Dual or Quad CPU complications? Grant
2012-12-13 6:23 ` Alan McKinnon
2012-12-13 7:36 ` Florian Philipp
2012-12-13 7:44 ` J. Roeleveld
2012-12-13 13:01 ` Luis Gustavo Vilela de Oliveira
2012-12-13 13:14 ` Rafa Griman
2012-12-13 14:13 ` Bruce Hill
2012-12-15 0:40 ` Mick
2012-12-15 11:49 ` Florian Philipp
2012-12-14 7:43 ` Grant
2012-12-14 8:47 ` Rafa Griman
2012-12-14 9:44 ` Grant
2012-12-14 10:03 ` Rafa Griman
2012-12-14 22:26 ` Grant
2012-12-15 3:16 ` Grant
2012-12-15 3:25 ` Michael Mol
2012-12-15 12:40 ` Florian Philipp
2012-12-15 17:56 ` Volker Armin Hemmann
2012-12-13 15:55 ` [gentoo-user] " James
2012-12-14 7:53 ` Rafa Griman
2012-12-13 18:18 ` [gentoo-user] " Michael Hampicke
2012-12-13 18:22 ` Volker Armin Hemmann
2012-12-14 7:55 ` Rafa Griman
2012-12-14 8:00 ` Grant
2012-12-15 17:49 ` Volker Armin Hemmann [this message]
2012-12-15 19:46 ` Grant
2012-12-15 19:57 ` J. Roeleveld
2012-12-16 12:52 ` Volker Armin Hemmann
2012-12-16 15:39 ` J. Roeleveld
2012-12-16 15:58 ` Michael Mol
2012-12-17 7:00 ` J. Roeleveld
2012-12-17 9:09 ` Michael Mol
2012-12-17 10:29 ` J. Roeleveld
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=1832535.yE7Zi1bxev@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=rafagriman@gmail.com \
/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