<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vetta project &#187; Hardware</title>
	<atom:link href="http://www.vetta.org/tag/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vetta.org</link>
	<description></description>
	<lastBuildDate>Thu, 22 Jul 2010 19:13:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>The innovator&#8217;s dilemma</title>
		<link>http://www.vetta.org/2009/02/the-innovators-dilemma/</link>
		<comments>http://www.vetta.org/2009/02/the-innovators-dilemma/#comments</comments>
		<pubDate>Sat, 28 Feb 2009 21:07:38 +0000</pubDate>
		<dc:creator>Shane Legg</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Economics]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Start-up]]></category>

		<guid isPermaLink="false">http://www.vetta.org/?p=155</guid>
		<description><![CDATA[The way in which technological change occurs in industries has always interested me. One quite well known book on this subject is &#8220;The Innovator&#8217;s Dilemma&#8221; by Clayton M. Christensen. Here&#8217;s a nice post on a friend&#8217;s blog that summarises the &#8230; <a href="http://www.vetta.org/2009/02/the-innovators-dilemma/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The way in which technological change occurs in industries has always interested me.  One quite well known book on this subject is &#8220;The Innovator&#8217;s Dilemma&#8221; by Clayton M. Christensen.  <a href="http://www.hartnall.com/2009/02/the-innovators-dilemma/">Here&#8217;s a nice post</a> on a friend&#8217;s blog that summarises the essential ideas.Â  The book contains many fascinating examples of disruptive changes and is certainly worth a read.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vetta.org/2009/02/the-innovators-dilemma/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tick, tock, tick, tock&#8230;</title>
		<link>http://www.vetta.org/2009/02/tick-tock-tick-tock/</link>
		<comments>http://www.vetta.org/2009/02/tick-tock-tick-tock/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 12:40:30 +0000</pubDate>
		<dc:creator>Shane Legg</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[AGI]]></category>
		<category><![CDATA[Computer Power]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Singularity]]></category>
		<category><![CDATA[Supercomputers]]></category>

		<guid isPermaLink="false">http://www.vetta.org/?p=144</guid>
		<description><![CDATA[I recently read about IBM&#8217;s Sequoia supercomputer that will be operational in 2011.  It will perform 20 Peta FLOPS and have 1.6 Peta bytes of RAM.  To put that in perspective: if it were to attempt to simulation a human &#8230; <a href="http://www.vetta.org/2009/02/tick-tock-tick-tock/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I recently read about IBM&#8217;s<a href="http://news.zdnet.co.uk/hardware/0,1000000091,39610058,00.htm"> Sequoia supercomputer</a> that will be operational in 2011.  It will perform 20 Peta FLOPS and have 1.6 Peta bytes of RAM.  To put that in perspective: if it were to attempt to simulation a human cerebral cortex it would be able to allocate 50 bytes of RAM and 700 calculations per second to every synapse in the model.  Unless the human brain is doing something pretty weird, the quest to build a computer with comparable raw processing power is almost over.</p>
<p>As I do at the start of each year, I&#8217;ve spent some time reconsidering when I think roughly human level AGI will exist.  I&#8217;ve again decided to leave it at 2025, but now with a reduced standard deviation of 5 years.  Computer power is a limitation as researchers typically have limited hardware budgets, unlike the DOD guys and their monster supercomputers.  From what I&#8217;ve read, computer power should continue to grow exponentially for at least the next 5 years, and probably the next 10.  So I don&#8217;t see this as being too much of an issue in the coming decade.  On the algorithm side, I think things are progressing really well.  I know a number of very talented people who are working on what I think are the key building blocks required before the construction of a basic AGI can begin.  I&#8217;m certain these problems are solvable, but whether it takes 2 years or 10 years is hard to guess.  This is my main source of uncertainty.</p>
<p><span id="more-144"></span>UPDATE 11 April 2009: Note that these predictions do not take into account my apparent bias towards predicting that things will happen faster than they actually do (see previous post).  The required compensation for technology events appears to be about 50% more time.  Thus if you want the &#8220;Shane meta predictor&#8221;, then take 2033 as the expected date, perhaps with a standard deviation of 7 years.  At least with financial markets I trust my meta predictor more than my straight predictions and thus I buy and sell accordingly to it.  So I suppose that if I had to put money on a date, I should go with 2033.  But don&#8217;t ask me why it&#8217;s going to take that long: I really don&#8217;t know.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vetta.org/2009/02/tick-tock-tick-tock/feed/</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>Learning to predict the future</title>
		<link>http://www.vetta.org/2009/02/learning-to-predict-the-future/</link>
		<comments>http://www.vetta.org/2009/02/learning-to-predict-the-future/#comments</comments>
		<pubDate>Sat, 07 Feb 2009 00:30:31 +0000</pubDate>
		<dc:creator>Shane Legg</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[AGI]]></category>
		<category><![CDATA[Computer Power]]></category>
		<category><![CDATA[future]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Singularity]]></category>

		<guid isPermaLink="false">http://www.vetta.org/?p=141</guid>
		<description><![CDATA[One of the things I&#8217;ve been thinking about recently is the prediction of the future.  Many people really enjoy doing this and come up with all sorts of wild speculations.  It&#8217;s kind of like having the liberty to write your &#8230; <a href="http://www.vetta.org/2009/02/learning-to-predict-the-future/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>One of the things I&#8217;ve been thinking about recently is the prediction of the future.  Many people really enjoy doing this and come up with all sorts of wild speculations.  It&#8217;s kind of like having the liberty to write your own science fiction, but then taking it a step further by convincing yourself to actually believe it.  Sooner or later the future arrives, and many of the recorded predictions look rather silly.  More cautions people take note of this and often avoid easily falsifiable predictions.  That&#8217;s all very well as it avoids them ending up looking like a fool, however it also makes becoming a better predictor problematic as they&#8217;re never really forced to contemplate their mistakes.  My preference is to make an honest attempt at specific predictions, along with the reasoning behind them.  Then when the time comes, go back over them and try to work out what went right, what went wrong, and mostly importantly why.  Was it bad luck?  Was I overconfident?  Under confident?  Was some kind of systematic bias at work?</p>
<p>One example of this has been trying to predict the medium term direction of the stock market over the last 15 years.  The evidence so far shows that I&#8217;m consistently good at predicting what will happen, but that I predict that it will happen much sooner than it actually does; I roughly need to double my time estimates.  I&#8217;m now trying to mentally correct for this bias in the trades I make, but it will take some years to see if this is working.</p>
<p><span id="more-141"></span>In technological matters, I&#8217;ve generally done quite well.  My picks for Sun, java, digital music, linux, MySQL and open source in general were pretty much on the mark.  I thought machine learning use in industry would be bigger than it is today, but I wasn&#8217;t too far off.  My biggest mistake was to badly underestimate how much Microsoft&#8217;s revenues would grow over the last 10 years &#8212; I thought they&#8217;d already almost saturated the market and its ability to pay.  Like stock markets, my most consistent error has been to be to predict that things will happen faster than they actually do.  I typically need to add about 50% to the time required.</p>
<p>As I don&#8217;t have a lot of my own technological predictions to look at, and some remain in the future, I&#8217;ve recently been looking at predictions made by others.  I found a few of my old computer and science magazines from the early 80&#8242;s through to the late 90&#8242;s which contained predictions, and I also dug up Kurzweil&#8217;s &#8220;The age of spiritual machines&#8221; written in 1999 in which he has a whole chapter about 2009.  There were a lot of hits and misses, but if I stand back and try to see the big picture, a pattern becomes clear: Predictions about basic hardware performance, even one I saw in a magazine from 25 years ago, are amazingly accurate.  But you probably knew that already.  Predictions about what would be technologically possible to do at a given point in time were not as accurate, but were still pretty good.  Where things really started to go wrong was when they tried to predict not what would be possible, but what the majority of people would actually be doing.</p>
<p>Perhaps some examples would best explain this.  State of the art speech recognition systems, such as some of the systems that were being developed at IDSIA when I was there, work impressively well.  However, once you&#8217;ve learnt to touch type it is typically easier, quieter, more convenient (especially when editing or coding) and far more private to use a keyboard.  I don&#8217;t care how good speech recognition is, I don&#8217;t want to sit in a room full of people talking out loud to their computers all day.  I only know one person who routinely uses speech recognition to input text.  The fact that speech recognition is technologically doable, doesn&#8217;t translate into it being practically useful for many everyday situations.</p>
<p>There are plenty of predictions that fail in this way: the prediction that everybody now would be making video calls on their cellphones.  It&#8217;s certainly technologically possible, I saw a guy with a phone that could do it two years ago, but almost nobody does it.  Or that most long distance air travel would be in supersonic jets.  Again, technologically possible, has been for a long time, but not done in practice.  Or that all mice would be wireless by now.  Technologically possible, has been for years, but as far as I can tell most new mice still have cords.  Or that most people driving long distance on freeways would get their car to automatically drive itself.  I&#8217;m sure that&#8217;s technologically possible, but I don&#8217;t see anybody doing it.  Or that your computer would log you in based on recognising your face or your voice.  Technologically possible today, but not done in practice.  And so on.</p>
<p>In short: Predicting raw performance is surprising accurate.  Predicting what will be possible using the knowledge and technology of some future date can also be done with moderate success.  Predicting what the population will routinely do, however, is much harder.  The latter is largely decided by habit, cost and convenience.  Simply being possible isn&#8217;t enough.  Note that predicting the development of the first powerful AGI is of the second type.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vetta.org/2009/02/learning-to-predict-the-future/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>2.4 Tera FLOPS per card</title>
		<link>http://www.vetta.org/2008/07/24-tera-flops-per-card/</link>
		<comments>http://www.vetta.org/2008/07/24-tera-flops-per-card/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 20:35:19 +0000</pubDate>
		<dc:creator>Shane Legg</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Computer Power]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Singularity]]></category>
		<category><![CDATA[Supercomputers]]></category>

		<guid isPermaLink="false">http://www.vetta.org/?p=70</guid>
		<description><![CDATA[Remember when I was raving about nVidia&#8217;s new GTX 280 graphics card that crunches 1 Tera FLOPS? Yeah, well, that was 3 weeks ago. Today, Radeon&#8217;s new HD 4870 X2 graphics card has 1600 stream processors that crunch 2.4 Tera &#8230; <a href="http://www.vetta.org/2008/07/24-tera-flops-per-card/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Remember when I was raving about nVidia&#8217;s new <a href="http://www.vetta.org/2008/06/super-computer-on-a-chip/">GTX 280</a> graphics card that crunches 1 Tera FLOPS?</p>
<p>Yeah, well, that was 3 weeks ago.</p>
<p>Today, Radeon&#8217;s new <a href="http://techreport.com/articles.x/15105">HD 4870 X2</a> graphics card has 1600 stream processors that crunch 2.4 Tera FLOPS.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vetta.org/2008/07/24-tera-flops-per-card/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Neural networks with Nvidia CUDA</title>
		<link>http://www.vetta.org/2008/06/neural-networks-with-nvidia-cuda/</link>
		<comments>http://www.vetta.org/2008/06/neural-networks-with-nvidia-cuda/#comments</comments>
		<pubDate>Mon, 09 Jun 2008 14:37:16 +0000</pubDate>
		<dc:creator>Shane Legg</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Computer Power]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Neural Networks]]></category>
		<category><![CDATA[Neuroscience]]></category>
		<category><![CDATA[nVidia]]></category>
		<category><![CDATA[Singularity]]></category>
		<category><![CDATA[Supercomputers]]></category>

		<guid isPermaLink="false">http://www.vetta.org/?p=59</guid>
		<description><![CDATA[If Roadrunner is a bit beyond your budget, simulating neural networks with GPUs might be an option: The next generation of Nvidia GPUs will support enhancements such as double precision floating point in order to make them more suitable for &#8230; <a href="http://www.vetta.org/2008/06/neural-networks-with-nvidia-cuda/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>If Roadrunner is a bit beyond your budget, simulating neural networks with GPUs might be an option:</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/lFUxIquFcQA&#038;hl=en"></param><embed src="http://www.youtube.com/v/lFUxIquFcQA&#038;hl=en" type="application/x-shockwave-flash" width="425" height="344"></embed></object></p>
<p>The next generation of Nvidia GPUs will support enhancements such as double precision floating point in order to make them more suitable for general purpose highly parallel computation.   There will also be cards with no graphics interface and greater maximum RAM designed specifically for low cost supercomputing applications.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.vetta.org/2008/06/neural-networks-with-nvidia-cuda/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
