 




<?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: why does the CPU&#8217;s speed greatly exceeds that of I/O devices</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/computation-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/computation-time/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 15:01:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/computation-time/#comment-79318</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Sat, 17 Jul 2010 01:27:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-79318</guid>
		<description><![CDATA[First, they are &lt;i&gt;designed&lt;/i&gt; to do different &lt;i&gt;kinds&lt;/i&gt; of things.

If we only think of i/O devices that are used for storage, for example, they are designed for &lt;i&gt;permanence&lt;/i&gt;. When the power is shut off, they don&#039;t forget what they are storing. But CPUs are designed for &lt;i&gt;rapid change without permanence&lt;/i&gt;. A significant change happens on every CPU cycle. The bits in a CPU don&#039;t need to retain their state for years; they&#039;ll switch to a different state in the next microsecond anyway.

In between I/O and CPU are other elements such as memory and cache. The characteristics of all of them are a balance between what&#039;s needed for a particular degree of permanence and a degree of switching speed. Micro-components that switch states extremely fast are not so good at retaining data.

Then there is distance. I/O devices tend to be farther away. The distance between L3 cache and actual logic units can be within the millimeter range, while a signal from an I/O device may be many centimeters away, or even meters. As fast as signals can travel, it still takes ten or a hundred times longer to travel ten or a hundred times as far.

And an I/O device generally doesn&#039;t &lt;i&gt;do&lt;/i&gt; anything until a CPU has processed instructions that result in a signal being sent to the I/O device. Most things done by an I/O device necessarily require some interaction through the CPU before and after the I/O device completes the request.

There are lots of reasons. But about the only useful answer is because they&#039;re designed and intended to do different things.

Tom]]></description>
		<content:encoded><![CDATA[<p>First, they are <i>designed</i> to do different <i>kinds</i> of things.</p>
<p>If we only think of i/O devices that are used for storage, for example, they are designed for <i>permanence</i>. When the power is shut off, they don&#8217;t forget what they are storing. But CPUs are designed for <i>rapid change without permanence</i>. A significant change happens on every CPU cycle. The bits in a CPU don&#8217;t need to retain their state for years; they&#8217;ll switch to a different state in the next microsecond anyway.</p>
<p>In between I/O and CPU are other elements such as memory and cache. The characteristics of all of them are a balance between what&#8217;s needed for a particular degree of permanence and a degree of switching speed. Micro-components that switch states extremely fast are not so good at retaining data.</p>
<p>Then there is distance. I/O devices tend to be farther away. The distance between L3 cache and actual logic units can be within the millimeter range, while a signal from an I/O device may be many centimeters away, or even meters. As fast as signals can travel, it still takes ten or a hundred times longer to travel ten or a hundred times as far.</p>
<p>And an I/O device generally doesn&#8217;t <i>do</i> anything until a CPU has processed instructions that result in a signal being sent to the I/O device. Most things done by an I/O device necessarily require some interaction through the CPU before and after the I/O device completes the request.</p>
<p>There are lots of reasons. But about the only useful answer is because they&#8217;re designed and intended to do different things.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meandyou</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/computation-time/#comment-79145</link>
		<dc:creator>meandyou</dc:creator>
		<pubDate>Tue, 13 Jul 2010 13:25:42 +0000</pubDate>
		<guid isPermaLink="false">#comment-79145</guid>
		<description><![CDATA[because electronics are fast that means that the core inside the processor is fast.
 
It is a physical device that reads the punch card (or the paper tape) and translates it to electronic form.]]></description>
		<content:encoded><![CDATA[<p>because electronics are fast that means that the core inside the processor is fast.</p>
<p>It is a physical device that reads the punch card (or the paper tape) and translates it to electronic form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.038 seconds using memcached
Object Caching 281/287 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 16:04:27 -->