The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Early Unix function calls: expensive?
Date: Mon, 4 Jan 2016 09:29:40 -0800	[thread overview]
Message-ID: <20160104172940.GE20207@mcvoy.com> (raw)
In-Reply-To: <6CCB0746-0243-4EA5-8171-D06A442D7D36@tfeb.org>

On Mon, Jan 04, 2016 at 08:52:51AM +0000, Tim Bradshaw wrote:
> On 4 Jan 2016, at 04:40, Armando Stettner <aps at ieee.org> wrote:
> 
> > I guess I experienced things a little differently: computer science basis notwithstanding, the VAX was hugely successful for DEC.
> 
> I think it was, too.  What I meant, though, was that, although x86
> demonstrates that it's possible to make almost anything fast by the
> application of sufficient money, the VAX was something which was expensive
> to keep performance-competitive, especially in the era when RISC could
> make really easy wins, and the cost of doing that hurt DEC pretty badly,
> I would expect (and made VAXes increasingly expensive compared to the
> competition, which I remember them being in the late 80s).  And I guess
> Alpha was too late.

Yeah, the 750 was OK [*], the 780 was nice, the 8600 (which UW-Madison
named "speedy.rsch.wisc.edu", such a bad name) was expensive.  They threw
a lot of hardware at the perf problem and it seems, to me at least, they
made a pretty good case for the RISC tradeoffs.  But those tradeoffs made
sense when transistors were expensive; these days x86 has shown you can
get some sweet perf out of that CISCy design (though I believe it's sort
of a RISC under the covers).

And as for Alpha, I never warmed up to it.  It was never fast for the 
workloads I cared about (build, test, file serving, integer stuff).
To me, it was over hyped and it under delivered.  Too bad, I liked 
DEC as a company.

[*] the 750 at the UW CS department was where they kept the BSD sources,
it was called slovax.  It was slow but I had so much fun reading that
code that I've always had a machine named slovax ever since, the current
one is mcvoy.com.


  reply	other threads:[~2016-01-04 17:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03 23:35 Warren Toomey
2016-01-03 23:53 ` Tim Bradshaw
2016-01-04  0:01   ` John Cowan
2016-01-04  4:40     ` Armando Stettner
2016-01-04  8:52       ` Tim Bradshaw
2016-01-04 17:29         ` Larry McVoy [this message]
2016-01-04 13:50       ` Clem Cole
2016-01-05  2:00       ` Ronald Natalie
2016-01-05 15:13         ` Clem Cole
2016-01-05 16:46           ` John Cowan
2016-01-05 17:33             ` Diomidis Spinellis
2016-01-05 17:42             ` Clem Cole
2016-01-05 17:28           ` Ronald Natalie
2016-01-05 17:43             ` Clem Cole
2016-01-05 17:46               ` Ronald Natalie
2016-01-05 18:03                 ` Warner Losh
2016-01-05 18:24                   ` Ronald Natalie
2016-01-05 20:26                     ` scj
2016-01-05 20:49                     ` John Cowan
2016-01-05 23:24         ` Dave Horsfall
2016-01-05 23:55           ` Ronald Natalie
2016-01-04  0:00 ` John Cowan
2016-01-04  0:42 ` scj
2016-01-04 11:35   ` Tony Finch
     [not found] <mailman.3.1451865187.15972.tuhs@minnie.tuhs.org>
2016-01-04  1:08 ` Johnny Billquist
2016-01-04  1:29   ` Larry McVoy
2016-01-04  1:31 Noel Chiappa
2016-01-04  2:24 ` scj
2016-01-04  4:24   ` Larry McVoy
2016-01-04  1:59 Norman Wilson
2016-01-04 15:09 ` John Cowan
2016-01-04  2:21 Clem Cole
2016-01-04 12:53 Noel Chiappa

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=20160104172940.GE20207@mcvoy.com \
    --to=lm@mcvoy.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).