From: Peter Fein <pfein@pobox.com>
To: linux-smp@vger.kernel.org
Subject: Kernel Support for Dual Core x86-64?
Date: Sat, 17 Sep 2005 17:41:47 -0500 [thread overview]
Message-ID: <432C9BAB.5060202@pobox.com> (raw)
Hi all-
My company is looking to build a cluster of Linux machines to run an
in-house compute-intensive application. We're strongly considering
dual-processor, dual-core x86-64 systems for cost reasons (shared
hardware, less rack space). I have a few questions, and despite
extensive googling, haven't been able to find satisfactory answers.
1. Can a dual core chip run two os-level *processes* simultaneously or
only two threads from the same process? Our processes (written in
Python, with parts in C) are completely independent of each other.
2. What sort of speed up relative to a dual processor, single core
system could I expect to gain? I realize this is highly application
dependent and I'm not looking for any hard figures. I just want to get
a rough idea to see if the additional cost is worth it.
3. Any suggestions on compiler version? We're currently using GCC-3.3.6
on our 32 bit boxes.
Thanks in advance!
--
Peter Fein pfein@pobox.com 773-575-0694
Basically, if you're not a utopianist, you're a schmuck. -J. Feldman
next reply other threads:[~2005-09-17 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 22:41 Peter Fein [this message]
2005-09-18 15:29 ` Kernel Support for Dual Core x86-64? Robert M. Hyatt
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=432C9BAB.5060202@pobox.com \
--to=pfein@pobox.com \
--cc=linux-smp@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).