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 16:54:25 -0700	[thread overview]
Message-ID: <CAK7dMtAmCKUUasYdL6f761RDvBuB9XHM3DJ6rYn_9FDFEJiYdQ@mail.gmail.com> (raw)
In-Reply-To: <20171229163832.GA17231@mcvoy.com>

I trust your judgement and experience WRT the Alpha.

If you're looking for massive performance deltas, what about ECL
designs like the IBM 3090 and Cray designs in the late '80s/ early
'90s?  I believe those were not a multiple but a magnitude faster than
contemporaries.

Regards,

On Fri, Dec 29, 2017 at 9:38 AM, Larry McVoy <lm at mcvoy.com> wrote:
> On Fri, Dec 29, 2017 at 04:04:01AM -0700, 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
>
> Wow, that first graph is the most misleading graph on CPU performance
> I've ever seen.  Ever.
>
> So from 1993 to 2000 the only CPUs released were Alphas?
>
> That era was when I was busy measuring performance across cpus and
> operating systems and I don't ever remember any processor being a
> factor of 2 better than its peers.  And maybe I missed it, I only
> owned a couple of alpha systems, but I never saw an Alpha that was
> a game changer.  Alpha was cool but it was too little, too late to
> save DEC.
>
> In that time period, even more so now, you had to be 2x better to get
> a customer to switch to your platform.
>
>         2x cheaper
>         2x faster
>         2x more reliable
>
> Do one of those and people would consider switching platforms.  Less than
> that was really tough and it was always, so far as I remember, less than
> that.  SMP might be an exception but we went through that whole learning
> process of "well, we advertised symmetric but when we said that what we
> really meant was you should lock your processes down to a processor
> because caches turn out to matter".  So in theory, N processors were N
> times faster than 1 but in practice not so much.
>
> I was very involved in performance work and cpu architecture and I'd love
> to be able to claim that we had a 2x faster CPU than someone else but we
> didn't, not at Sun and not at SGI.
>
> It sort of make sense that there weren't huge gaps, everyone was more or
> less using the same sized transistors, the same dram, the same caches.
> There were variations, Intel had/has the biggest and most advanced
> foundries but IBM would push the state of the art, etc.  But I don't
> remember anyone ever coming out with a chip that was 2x faster.  I
> suspect you can find one where chip A is introduced at the end of chip
> B's lifespan and A == 2*B but wait a few month's and B gets replaced
> and A == .9*C.
>
> Can anyone point to a 2x faster than it's current peers chip introduction?
> Am I just not remembering one or is that not a thing?
>
> --lm


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

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 16:38 Larry McVoy
2017-12-29 23:54 ` Kevin Bowling [this message]
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
  -- 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-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
2017-12-29 23:58           ` Larry McVoy
     [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=CAK7dMtAmCKUUasYdL6f761RDvBuB9XHM3DJ6rYn_9FDFEJiYdQ@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).