From: "Lyndon Nerenberg (VE6BBM/VE7TFX)" <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: Re: [9fans] Parallelism is over a barrel(fish)?
Date: Mon, 19 Oct 2009 18:04:24 -0600 [thread overview]
Message-ID: <d3012e90b0fed10cc3208df42b022c8a@yyc.orthanc.ca> (raw)
In-Reply-To: <13426df10910181312i7ec404b0t6e6a83899bef62e6@mail.gmail.com>
>From last week's ACM Technews ...
Why Desktop Multiprocessing Has Speed Limits
Computerworld (10/05/09) Vol. 43, No. 30, P. 24; Wood, Lamont
Despite the mainstreaming of multicore processors for desktops, not
every desktop application can be rewritten for multicore frameworks,
which means some bottlenecks will persist. "If you have a task that
cannot be parallelized and you are currently on a plateau of
performance in a single-processor environment, you will not see that
task getting significantly faster in the future," says analyst Tom
Halfhill. Adobe Systems' Russell Williams points out that performance
does not scale linearly even with parallelization on account of memory
bandwidth issues and delays dictated by interprocessor communications.
Analyst Jim Turley says that, overall, consumer operating systems
"don't do anything smart" with multicore architecture. "We have to
reinvent computing, and get away from the fundamental premises we
inherited from von Neumann," says Microsoft technical fellow Burton
Smith. "He assumed one instruction would be executed at a time, and
we are no longer even maintaining the appearance of one instruction at
a time." Analyst Rob Enderle notes that most applications will operate
on only a single core, which means that the benefits of a multicore
architecture only come when multiple applications are run. "What we'd
all like is a magic compiler that takes yesterday's source code and
spreads it across multiple cores, and that is just not happening,"
says Turley. Despite the performance issues, vendors prefer multicore
processors because they can facilitate a higher level of power
efficiency. "Using multiple cores will let us get more performance
while staying within the power envelope," says Acer's Glenn Jystad.
http://www.computerworld.com/s/article/342870/The_Desktop_Traffic_Jam?intsrc=print_latest
next prev parent reply other threads:[~2009-10-20 0:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 19:09 [9fans] Barrelfish Tim Newsham
2009-10-14 19:54 ` Roman Shaposhnik
2009-10-14 21:21 ` Tim Newsham
2009-10-14 21:33 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2009-10-14 21:42 ` Noah Evans
2009-10-14 21:45 ` erik quanstrom
2009-10-14 21:57 ` Noah Evans
2009-10-14 22:10 ` Eric Van Hensbergen
2009-10-14 22:21 ` Noah Evans
2009-10-15 1:03 ` David Leimbach
2009-10-15 1:50 ` Roman Shaposhnik
2009-10-15 2:12 ` Eric Van Hensbergen
2009-10-15 10:53 ` Sam Watkins
2009-10-15 11:50 ` Richard Miller
2009-10-15 12:00 ` W B Hacker
2009-10-16 17:03 ` Sam Watkins
2009-10-16 18:17 ` ron minnich
2009-10-16 18:39 ` Wes Kussmaul
2009-10-17 12:42 ` Roman Shaposhnik
2009-10-15 11:56 ` Josh Wood
2009-10-15 13:11 ` hiro
2009-10-15 15:05 ` David Leimbach
2009-10-18 1:15 ` Roman Shaposhnik
2009-10-18 3:15 ` Bakul Shah
[not found] ` <e763acc10910180606q1312ff7cw9a465d6af39c0fbe@mail.gmail.com>
2009-10-18 13:22 ` Roman Shaposhnik
2009-10-18 19:18 ` Bakul Shah
2009-10-18 20:12 ` ron minnich
2009-10-20 0:04 ` Lyndon Nerenberg (VE6BBM/VE7TFX) [this message]
2009-10-20 1:11 ` [9fans] Parallelism is over a barrel(fish)? W B Hacker
2009-10-14 21:36 ` [9fans] Barrelfish Eric Van Hensbergen
2009-10-15 2:05 ` Roman Shaposhnik
2009-10-15 2:17 ` Eric Van Hensbergen
2009-10-15 3:32 ` Tim Newsham
2009-10-15 3:59 ` Eric Van Hensbergen
2009-10-15 17:39 ` Tim Newsham
2009-10-15 18:28 ` Christopher Nielsen
2009-10-15 18:55 ` W B Hacker
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=d3012e90b0fed10cc3208df42b022c8a@yyc.orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
/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).