The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: kevin.bowling@kev009.com (Kevin Bowling)
Subject: [TUHS] Why did PDPs become so popular?
Date: Fri, 29 Dec 2017 04:04:01 -0700	[thread overview]
Message-ID: <CAK7dMtDK2=VjcQYpTY7xHCu2CCxrQ50+bz_wxMPFMDEFFNOexw@mail.gmail.com> (raw)
In-Reply-To: <20171228232852.GC30269@thunk.org>

I can mostly only comment from my readings, but this is IMHO a
non-trivial question even in retrospect because it depends on what you
or your workload valued.  I do like how lmbench categorizes across
multiple "interesting" vectors, showing some of the design tradeoffs
of CPU architecture and then how the OS plays a role in real world
applications.

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

For intel the Pentium Pro was pivotal in being able to position vs the
contemporary RISC CPUs with multi-MB caches.  And federating cost
effective CPUs together with Laissez-faire mainboard/system
packaging/OSes turned out to be more important than pretty much
anything else.

I know that IBM Austin did some wizard of oz stuff in early POWER..
Bi-CMOS superscalar that put it 4-5 years ahead of most competing
microprocessor designs in floating point, though SGI and HP traded
respectable volleys.  But POWER also had fat memory bandwidth, they
tended to make well balanced braniacs that didn't blindly pursue the
clockspeed war (http://www.cs.virginia.edu/~mccalpin/papers/balance/).
They got into a weird spot in the second half of the 90s with an
out-dated bus, internal competition from PowerPC and RS64, but
returned to leadership with POWER4 and up to today. POWER's IO
leadership made it a good fit for many early internet routers in the
early '90s, NSFNET and others.  Interestingly modern POWER retains
that leadership on memory and I/O which can put it 2 to 4 years ahead
of everything else depending on what you value (Google seems to see
the light using it for gluing GPUs together..).  From IBM Rochester,
RS64 was kind of interesting in being the first use of SMT and having
incredibly low TDP which were both interesting clairvoyance into the
next decade.

In retrospect I don't think SPARC ever had a reasonable showing pound
for pound vs other microprocessors :)

Regards,

On Thu, Dec 28, 2017 at 4:28 PM, Theodore Ts'o <tytso at mit.edu> wrote:
> On Thu, Dec 28, 2017 at 08:08:11AM -0800, Larry McVoy wrote:
>> > I think you're right.  The disinterest in marketing and advertising
>> > (Ken Olsen, and therefore DEC, had a "build it and they will come"
>> > mentality) was one aspect of the corporate culture.  An example of its
>> > negative impact:  When the Alpha EV5 came out, it was several times
>> > faster than anything else around.
>>
>> Got a reference for that performance claim?  Wasn't that mid 1990's?
>> If so, I was heavily into benchmarking and performance work during
>> that period.  If there was a processor that was 2x faster, let alone
>> several times faster, I would have noticed.
>>
>> http://www.bitmover.com/lmbench/lmbench-usenix.pdf
>
> "Digital's 21164 Reaches 500 MHz: Alpha Regains Performance Lead,
> Leaves Pentium Pro in Dust" -- Microprocessor Report July 8, 1996.
>
> http://noel.feld.cvut.cz/vyu/scs/alpha/164_500.pdf
>
> Looks to me from the article that Alpha was certain participating in
> the clock speed wars, though.
>
>                                         - Ted


  reply	other threads:[~2017-12-29 11:04 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 [this message]
2017-12-29 23:35         ` Jon Forrest
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='CAK7dMtDK2=VjcQYpTY7xHCu2CCxrQ50+bz_wxMPFMDEFFNOexw@mail.gmail.com' \
    --to=kevin.bowling@kev009.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).