<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Multicore Crisis?</title>
	<atom:link href="http://blog.mischel.com/2008/08/04/multicore-crisis/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mischel.com/2008/08/04/multicore-crisis/</link>
	<description>Musings on technology and life</description>
	<pubDate>Tue, 06 Jan 2009 00:48:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roy Harvey</title>
		<link>http://blog.mischel.com/2008/08/04/multicore-crisis/comment-page-1/#comment-3437</link>
		<dc:creator>Roy Harvey</dc:creator>
		<pubDate>Thu, 07 Aug 2008 19:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/?p=155#comment-3437</guid>
		<description>I'm not worried about a multi-core crisis as I am about the absence of fundamental changes to processor architecture to support it.  Maybe I just don't read the right sort of articles, but it appears that we are getting a lot of single processors stuck together, not an architecture built around parallelism.

But hey, what do I know?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not worried about a multi-core crisis as I am about the absence of fundamental changes to processor architecture to support it.  Maybe I just don&#8217;t read the right sort of articles, but it appears that we are getting a lot of single processors stuck together, not an architecture built around parallelism.</p>
<p>But hey, what do I know?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HunterW</title>
		<link>http://blog.mischel.com/2008/08/04/multicore-crisis/comment-page-1/#comment-3383</link>
		<dc:creator>HunterW</dc:creator>
		<pubDate>Tue, 05 Aug 2008 22:20:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/?p=155#comment-3383</guid>
		<description>Also ilya, I enjoyed Cilk's e-Book, great job! Even though you didn't mention DataRush ;)

HunterW
http://www.pervasivedatarush.com</description>
		<content:encoded><![CDATA[<p>Also ilya, I enjoyed Cilk&#8217;s e-Book, great job! Even though you didn&#8217;t mention DataRush ;)</p>
<p>HunterW<br />
<a href="http://www.pervasivedatarush.com" rel="nofollow">http://www.pervasivedatarush.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HunterW</title>
		<link>http://blog.mischel.com/2008/08/04/multicore-crisis/comment-page-1/#comment-3382</link>
		<dc:creator>HunterW</dc:creator>
		<pubDate>Tue, 05 Aug 2008 22:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/?p=155#comment-3382</guid>
		<description>&lt;cite&gt;The idea is to construct a program that operates in an assembly line fashion. For example, consider a program that gathers input, does some complex processing of the input data, and then generates some output.&lt;/cite&gt;
Often you can even parallelize the complex processing of the input data, using the dataflow programming paradigm, for even more concurrency.  At Pervasive Software we are developing a Java Library, called DataRush, to develop parallel data-intensive applications based on this paradigm.  We’ll be uploading our first release candidate later this week on our webpage, we would love it if you came for a free download!

HunterW
http://www.pervasivedatarush.com</description>
		<content:encoded><![CDATA[<p><cite>The idea is to construct a program that operates in an assembly line fashion. For example, consider a program that gathers input, does some complex processing of the input data, and then generates some output.</cite><br />
Often you can even parallelize the complex processing of the input data, using the dataflow programming paradigm, for even more concurrency.  At Pervasive Software we are developing a Java Library, called DataRush, to develop parallel data-intensive applications based on this paradigm.  We’ll be uploading our first release candidate later this week on our webpage, we would love it if you came for a free download!</p>
<p>HunterW<br />
<a href="http://www.pervasivedatarush.com" rel="nofollow">http://www.pervasivedatarush.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ilya</title>
		<link>http://blog.mischel.com/2008/08/04/multicore-crisis/comment-page-1/#comment-3369</link>
		<dc:creator>ilya</dc:creator>
		<pubDate>Tue, 05 Aug 2008 04:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/?p=155#comment-3369</guid>
		<description>Jim,

I like your 4-level model.  One thing I've seen  is, among the software developers I've talked with, something like 25-40% fall into #4.  I think the early apps to go multicore will be the scientific/engineering apps, graphics, etc.  But I bet by the time 8- or 16-core machines are around (which will be within one or two more chip cycles), it will be a competitive imperative to multicore-enable one's software.  I remember a couple years ago, one of the Cadalyst benchmarks tested a new dual-core workstation, and for the first time pretty much all the CAD apps were slower on it than on the previous generation.

My sense is that the chips arrived 4-5 years ahead of software tools to adequately program them.  But the vast majority of app developers have not yet moved their software to multicore.


[Also, for what it's worth - we at Cilk Arts have recently published an e-Book on multicore programming.  covers programming approaches including OpenMP, Intel's TBB, Pthreads, Cilk++, MPI. http://www.cilk.com/multicore-e-book ]</description>
		<content:encoded><![CDATA[<p>Jim,</p>
<p>I like your 4-level model.  One thing I&#8217;ve seen  is, among the software developers I&#8217;ve talked with, something like 25-40% fall into #4.  I think the early apps to go multicore will be the scientific/engineering apps, graphics, etc.  But I bet by the time 8- or 16-core machines are around (which will be within one or two more chip cycles), it will be a competitive imperative to multicore-enable one&#8217;s software.  I remember a couple years ago, one of the Cadalyst benchmarks tested a new dual-core workstation, and for the first time pretty much all the CAD apps were slower on it than on the previous generation.</p>
<p>My sense is that the chips arrived 4-5 years ahead of software tools to adequately program them.  But the vast majority of app developers have not yet moved their software to multicore.</p>
<p>[Also, for what it's worth - we at Cilk Arts have recently published an e-Book on multicore programming.  covers programming approaches including OpenMP, Intel's TBB, Pthreads, Cilk++, MPI. <a href="http://www.cilk.com/multicore-e-book" rel="nofollow">http://www.cilk.com/multicore-e-book</a> ]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
