The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] PDP-11 legacy, C, and modern architectures
Date: Thu, 28 Jun 2018 16:37:49 -0400	[thread overview]
Message-ID: <20180628163749.24410d93@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <20180628160202.GF21688@mcvoy.com>

So lets not forget: the original question was, do people need to do a
lot of parallel and concurrent computing these days. Keep that in
mind while thinking about this.

On Thu, 28 Jun 2018 09:02:02 -0700 Larry McVoy <lm@mcvoy.com> wrote:
> But for people who care about performance, and there are a lot of
> them, more but slower is less desirable than less but faster.

Sure, but where can you get fewer but faster any more? Yes, you can
get it up to a point, but that point tops out fast. Yes, you can get a
4GHz processor from Intel instead of a bunch of fairly low end
Broadcom ARM chips. However, that top end Intel chip isn't much faster
than it was a few years ago, and it's a pretty cheap and slow chip
compared to what people need, so one of them still isn't going to do
it for you, and so you still need to go parallel, and that means you
still need to write parallel code.

Thirty years ago, you could pay as much money as you wanted, up to
tens of millions, to get a faster single CPU for your work. The
difference between the processors on an IBM PC class machine and on a
Cray was Really Really Different. These days, Intel won't sell you
anything that costs more than a couple thousand dollars, and that
couple thousand dollar thing has many CPUs. The most you can pay per
core, for the highest end, is in the low hundreds depending on the
moment. Taking inflation into account, that's a silly low amount of
money. IBM will sell you some slightly more expensive high end POWER
stuff, but very few people buy that and besides that, there's pretty
much nothing.

So it doesn't matter even if you'd rather spend 100x to get a core
that's 10x faster than the top of what is offered, the 10x faster
thing doesn't exist. You're stuck. You've got top of the line 64 bit
x86 and maybe POWER and there's nothing else. 

So, yes, I agree, all things being equal, people will prefer to buy
the faster stuff, but at the moment, no one can get it, so instead,
we're in an age of loads of parallel machines and cores. Your maximal
fast core is in the hundreds of dollars, but you've got millions of
dollars of computing to do, so you buy tons of processors instead.

> People still care about performance and always will.  Yeah, for your
> laptop or whatever you could probably use what you have for the next
> 10 years and be fine.   But when you are doing real work, sorting
> the genome, machine learning, whatever, performance is a thing and
> lots of wimpy cpus are not.

For all those pieces of work, people use hundreds, thousands, or
hundreds of thousands of cores, depending on the job. Machine
learning, shotgun sequencing, etc., all depend on parallelism these
days. Sometimes people need to buy top end processors for that, but
even then, they have to buy a _ton_ of top end processors because any
given one is too small to do a significant fraction of the work.

So, circling back to the original discussion, languages that don't
let you express such algorithms well are now a problem.

Perry
-- 
Perry E. Metzger		perry@piermont.com

  parent reply	other threads:[~2018-06-28 20:38 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 17:54 Nelson H. F. Beebe
2018-06-26 18:03 ` Cornelius Keck
2018-06-26 21:21   ` Nelson H. F. Beebe
2018-06-26 21:56   ` Kurt H Maier
2018-06-26 18:52 ` Ronald Natalie
2018-06-26 19:01 ` Ronald Natalie
2018-06-26 21:16   ` Arthur Krewat
2018-06-26 21:50     ` Larry McVoy
2018-06-26 21:54       ` Ronald Natalie
2018-06-26 21:59         ` Larry McVoy
2018-06-26 22:20           ` Bakul Shah
2018-06-26 22:33             ` Arthur Krewat
2018-06-26 23:53               ` Bakul Shah
2018-06-27  8:30             ` Tim Bradshaw
2018-06-26 22:33           ` Andy Kosela
2018-06-27  0:11             ` Bakul Shah
2018-06-27  6:10               ` arnold
2018-06-27  2:18           ` [TUHS] PDP-11 legacy, C, and modern architectTures Theodore Y. Ts'o
2018-06-27  2:22             ` Theodore Y. Ts'o
2018-06-28 14:36             ` Steffen Nurpmeso
2018-06-27 11:26         ` [TUHS] PDP-11 legacy, C, and modern architectures Tony Finch
2018-06-27 14:33           ` Clem Cole
2018-06-27 14:38             ` Clem Cole
2018-06-27 15:30             ` Paul Winalski
2018-06-27 16:55               ` Tim Bradshaw
2018-06-27  6:27     ` arnold
2018-06-27 16:00 ` Steve Johnson
2018-06-28  4:12   ` Bakul Shah
2018-06-28 14:15     ` Theodore Y. Ts'o
2018-06-28 14:40       ` Larry McVoy
2018-06-28 14:55         ` Perry E. Metzger
2018-06-28 14:58           ` Larry McVoy
2018-06-28 15:39             ` Tim Bradshaw
2018-06-28 16:02               ` Larry McVoy
2018-06-28 16:41                 ` Tim Bradshaw
2018-06-28 16:59                   ` Paul Winalski
2018-06-28 17:09                   ` Larry McVoy
2018-06-29 15:32                     ` tfb
2018-06-29 16:09                       ` Perry E. Metzger
2018-06-29 17:51                       ` Larry McVoy
2018-06-29 18:27                         ` Tim Bradshaw
2018-06-29 19:02                         ` Perry E. Metzger
2018-06-28 20:37                 ` Perry E. Metzger [this message]
2018-06-28 15:37         ` Clem Cole
2018-06-28 20:37           ` Lawrence Stewart
2018-06-28 14:43       ` Perry E. Metzger
2018-06-28 14:56         ` Larry McVoy
2018-06-28 15:07           ` Warner Losh
2018-06-28 19:42           ` Perry E. Metzger
2018-06-28 19:55             ` Paul Winalski
2018-06-28 20:42             ` Warner Losh
2018-06-28 21:03               ` Perry E. Metzger
2018-06-28 22:29                 ` Theodore Y. Ts'o
2018-06-29  0:18                   ` Larry McVoy
2018-06-29 15:41                     ` Perry E. Metzger
2018-06-29 18:01                       ` Larry McVoy
2018-06-29 19:07                         ` Perry E. Metzger
2018-06-29  5:58                   ` Michael Kjörling
2018-06-28 20:52             ` Lawrence Stewart
2018-06-28 21:07               ` Perry E. Metzger
2018-06-28 16:45       ` Paul Winalski
2018-06-28 20:47         ` Perry E. Metzger
2018-06-29 15:43         ` emanuel stiebler
2018-06-29  2:02       ` Bakul Shah
2018-06-29 12:58         ` Theodore Y. Ts'o
2018-06-29 18:41           ` Perry E. Metzger
2018-06-29  1:02 Noel Chiappa
2018-06-29  1:06 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=20180628163749.24410d93@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=lm@mcvoy.com \
    --cc=tuhs@minnie.tuhs.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 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).