The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: nobozo@gmail.com (Jon Forrest)
Subject: [TUHS] Why did PDPs become so popular?
Date: Fri, 29 Dec 2017 15:35:27 -0800	[thread overview]
Message-ID: <12de637f-b6fc-cc24-ce33-40d4a5f1e475@gmail.com> (raw)
In-Reply-To: <CAK7dMtDK2=VjcQYpTY7xHCu2CCxrQ50+bz_wxMPFMDEFFNOexw@mail.gmail.com>



On 12/29/2017 3:04 AM, Kevin Bowling wrote:

> Alpha generally maintained integer/ALU and clockspeed leadership for
> most of the '90s
> http://www.cs.columbia.edu/~sedwards/classes/2012/3827-spring/advanced-arch-2011.pdf

I worked in the Computer Science Dept. at UC Berkeley in the 1990s
when Richard Sites, the chief architect of the Alpha, gave a talk
describing the Alpha. I remember him saying that there was nothing
out there from any other vendor that would be able to compete with
the Alpha for the next 10 years (I'm pretty sure he said 10 years but
it might have been longer).

Because I was the system manager for the Sequoia 2000 project, DEC's big
external research project after Project Athena, I got the first Alpha
delivered to UC Berkeley. I remember it being quite fast, although I
don't recall any specific benchmarks. The OS (OSF/1) was fairly
primitive as first and didn't even support multiple processor systems.
We were able to port Postgres to it fairly quickly in spite of various
issues related to the 64-bit Alpha architecture. In fact, the Postgres
group was using Alpha desktops when SQL was added to Postgres.

As nice as the Alphas were, I don't recall any compelling reason we
would have used them if we had to pay for them. In fact, at the same
time Mike Stonebraker and I wrote a grant proposal to Sun to get a
couple of SparcStation 10s to use to port Postgres to Solaris. The
SparcStations were just as nice to use as the Alphas.

DEC's later demise was quite sad to me, since before joining UC Berkeley
I had been a VAX/VMS person. DEC did a great job supporting Project
Sequoia 2000, and they were very generous with both their hardware and
money. Judging from Sites' presentation, they thought they were going
to win.

Jon Forrest



  reply	other threads:[~2017-12-29 23:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 14:05 Noel Chiappa
2017-12-28 15:59 ` Paul Winalski
2017-12-28 16:08   ` Larry McVoy
2017-12-28 23:28     ` Theodore Ts'o
2017-12-29 11:04       ` Kevin Bowling
2017-12-29 23:35         ` Jon Forrest [this message]
2017-12-29 23:58           ` Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2017-12-31  5:20 Rudi Blom
2017-12-31 12:56 ` Clement T. Cole
2017-12-31 15:03   ` Steve Simon
2017-12-29 16:38 Larry McVoy
2017-12-29 23:54 ` Kevin Bowling
2017-12-30  0:04   ` Larry McVoy
2017-12-30  0:54   ` Lawrence Stewart
2017-12-30  1:47     ` Kevin Bowling
2017-12-30  2:19       ` Lawrence Stewart
2017-12-30  2:35         ` Paul Winalski
2017-12-30  2:20       ` Paul Winalski
2017-12-31  2:47     ` Henry Bent
2017-12-30  1:07   ` Ron Natalie
2017-12-30  2:30     ` Paul Winalski
2017-12-31  3:00       ` Henry Bent
2017-12-31  9:59         ` Arrigo Triulzi
2017-12-31 15:55         ` Paul Winalski
     [not found] <109152082.5216233.1514413535270.ref@mail.yahoo.com>
2017-12-27 22:25 ` Dave Ritchie
2017-12-27 22:32   ` Dave Horsfall
2017-12-27 23:44     ` Paul Winalski
2017-12-27 23:38   ` Kevin Bowling
2017-12-28  0:07     ` Paul Winalski
2017-12-28  0:45       ` Kevin Bowling
2017-12-28  1:39       ` Ron Natalie
2017-12-27 21:02 Alec Muffett
2017-12-27 21:50 ` Grant Taylor
2017-12-28  1:23   ` Alec Muffett
2017-12-27 21:51 ` Clem Cole
2017-12-27 21:52   ` Clem Cole
2017-12-28  2:14   ` Greg 'groggy' Lehey

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=12de637f-b6fc-cc24-ce33-40d4a5f1e475@gmail.com \
    --to=nobozo@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;
as well as URLs for NNTP newsgroup(s).