From: Lamar Owen <lowen@pari.edu>
To: sparclinux@vger.kernel.org
Subject: Re: Sun Enterprise 6500. 10xUltraSPARC/400MHz, 10Gb mem
Date: Fri, 24 Mar 2006 19:08:46 +0000 [thread overview]
Message-ID: <200603241408.47256.lowen@pari.edu> (raw)
In-Reply-To: <87d5gegxf3.fsf@pumba.bayour.com>
On Thursday 23 March 2006 23:08, Dennis Jenkins wrote:
> I have a 8 processor E3500. Linux (Gentoo for me)
> works great, except that it CAN NOT use the internal
> Fiber Channel disk array.
Where did this information come from? I also have an E3500, and four 36.4GB
drives....
> Just remember that the CPUs themselves run at 334MHz
> or 400 MHZ. An E6500 only does 334MHz b/c the
> back-plane is too long to support faster CPUs.
The 400MHz/8MB cache CPU's can do a 5x multiplier with the right clock board,
with the gigaplane running at 80MHz and the CPU's at 400. This is what I
have in mine.
> I/O. In my opnion, the box would make a great
> database server, but would not be useful for high-end
> math or 3-d applications.
Mine is going to be a Plone ZEO client cluster, fronted by Pound.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu
next prev parent reply other threads:[~2006-03-24 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 18:13 Sun Enterprise 6500. 10xUltraSPARC/400MHz, 10Gb mem Turbo Fredriksson
2006-03-22 18:31 ` Jima
2006-03-22 19:21 ` Dennis Gilmore
2006-03-22 20:20 ` David S. Miller
2006-03-23 19:29 ` Lamar Owen
2006-03-23 20:11 ` David S. Miller
2006-03-23 20:30 ` Lamar Owen
2006-03-24 4:08 ` Dennis Jenkins
2006-03-24 19:08 ` Lamar Owen [this message]
2006-03-24 22:33 ` David S. Miller
2006-03-25 0:30 ` Lamar Owen
2006-03-25 0:36 ` David S. Miller
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=200603241408.47256.lowen@pari.edu \
--to=lowen@pari.edu \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.