<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Chris Cooper's Tech Blog</title>
	<atom:link href="http://roguepc.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://roguepc.wordpress.com</link>
	<description>Technical blog regarding PCs, web stuff, and more.</description>
	<lastBuildDate>Sat, 07 Apr 2007 00:44:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='roguepc.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Chris Cooper's Tech Blog</title>
		<link>http://roguepc.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://roguepc.wordpress.com/osd.xml" title="Chris Cooper&#039;s Tech Blog" />
	<atom:link rel='hub' href='http://roguepc.wordpress.com/?pushpress=hub'/>
		<item>
		<title>An explanation of &#8220;dual core&#8221; CPU / Processors</title>
		<link>http://roguepc.wordpress.com/2007/04/06/an-explanation-of-dual-core-cpu-processors/</link>
		<comments>http://roguepc.wordpress.com/2007/04/06/an-explanation-of-dual-core-cpu-processors/#comments</comments>
		<pubDate>Sat, 07 Apr 2007 00:40:45 +0000</pubDate>
		<dc:creator>roguepc</dc:creator>
				<category><![CDATA[Technical Articles]]></category>

		<guid isPermaLink="false">http://roguepc.wordpress.com/2007/04/06/an-explanation-of-dual-core-cpu-processors/</guid>
		<description><![CDATA[Article Technical Level: Novice One of the latest trends in CPU / processor technology is &#8220;dual core&#8221; or &#8220;multi core&#8221; processors. Processors previously designed all sit on one chip, with one core. The core does all the logic and thinking while the &#8220;chip&#8221; connects the core to the rest of the system and handles the [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=5&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Article Technical Level: <strong>Novice</strong></p>
<p>One of the latest trends in CPU / processor technology is &#8220;dual core&#8221; or &#8220;multi core&#8221; processors.  Processors previously designed all sit on one chip, with one core.  The core does all the logic and thinking while the &#8220;chip&#8221; connects the core to the rest of the system and handles the requests, houses the cache (onboard memory), and other logic activities.  Dual Core means there is litterally 2 cores sitting on a single chip.  Intel was the first to accomplish this feat with the release of the Pentium D series.  The Pentium D was labeled by the tech community to be a very inelegant way of implementing dual core as it essentially was 2 Pentium 4 cores slapped together on a single to form Pentium D.  This meant that very little was done to optimize the process.  AMD soon followed up with its Athlon X2 series which was regarded as a much more elegant and true to purpose Dual Core design.</p>
<p>Dual Core CPU&#8217;s usually run slightly lower clockspeeds (per core) then the higher end single core processors.  This is generally to help cut costs as well as maintain a safe thermal envelope.  Having 2 cores in such close proximity creates significantly more heat and as such, the first dual core processors had significantly lower clockspeeds (per core).</p>
<a class="DiggThisButton DiggMedium" href="http://digg.com/submit?url=http%3A%2F%2Froguepc.wordpress.com%2F2007%2F04%2F06%2Fan-explanation-of-dual-core-cpu-processors%2F&amp;title=An+explanation+of+%26%238220%3Bdual+core%26%238221%3B+CPU+%2F%26nbsp%3BProcessors"></a>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/roguepc.wordpress.com/5/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/roguepc.wordpress.com/5/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/roguepc.wordpress.com/5/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/roguepc.wordpress.com/5/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/roguepc.wordpress.com/5/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=5&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://roguepc.wordpress.com/2007/04/06/an-explanation-of-dual-core-cpu-processors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6c37e4db064c08c845cdb67d95ccac9?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">roguepc</media:title>
		</media:content>
	</item>
		<item>
		<title>An explanation of DDR versus DDR2</title>
		<link>http://roguepc.wordpress.com/2007/03/22/an-explanation-of-ddr-versus-ddr2/</link>
		<comments>http://roguepc.wordpress.com/2007/03/22/an-explanation-of-ddr-versus-ddr2/#comments</comments>
		<pubDate>Thu, 22 Mar 2007 13:53:05 +0000</pubDate>
		<dc:creator>roguepc</dc:creator>
				<category><![CDATA[Technical Articles]]></category>

		<guid isPermaLink="false">http://roguepc.wordpress.com/2007/03/22/an-explanation-of-ddr-versus-ddr2/</guid>
		<description><![CDATA[Article Technical Level: Intermediate RAM: Vendors randomly decide to list their ram speeds based on a &#8220;PCXXXX&#8221; standard or a MHz standard, they convert based on a formula related to data transfer rates. PC2100 = 266 MHz, PC3200 = 400 MHz, PC4200 = 533 MHz, PC5300 = 667 MHz, PC6400 = 800 MHz. There is [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=4&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Article Technical Level: <strong>Intermediate</strong></p>
<p>RAM:  Vendors randomly decide to list their ram speeds based on a &#8220;PCXXXX&#8221; standard or a MHz standard, they convert based on a formula related to data transfer rates.  PC2100 = 266 MHz, PC3200 = 400 MHz, PC4200 = 533 MHz, PC5300 = 667 MHz, PC6400 = 800 MHz.  There is of course more divisions inbetween, before, and after but these are the big ones.  Something that needs to be considered though is there is also DDR(1) and DDR2.  The original DDR has &#8220;latency&#8221; (time for data to get from one point to another) significantly lower then DDR2.  This is sort of like how cache differences work.  DDR2 was designed with higher latencies (bad) but higher bandwidth as well (good).  DDR(1) generally ends at PC3200 (highest official bandwidth of DDR) and DDR2 generally starts at PC4200.  The PC4200 / 533 MHz, again, refers to bandwidth.  This is how many megabytes (MB) per second are possible to transfer across the memory bus.  Again though, DDR2 has significantly higher latencies so it takes longer for that larger amount of data to get where it&#8217;s going.  The industry can&#8217;t seem to decide on a standard but over the last few years it has migrated to DDR2 due to lower costs.  DDR2 also uses less energy as compared to DDR due to higher efficiencies, a smaller manufacturing process and less power intensive design.  Very extreme performance nuts still tend to prefer DDR(1) due to its significantly lower latencies. </p>
<a class="DiggThisButton DiggMedium" href="http://digg.com/submit?url=http%3A%2F%2Froguepc.wordpress.com%2F2007%2F03%2F22%2Fan-explanation-of-ddr-versus-ddr2%2F&amp;title=An+explanation+of+DDR+versus%26nbsp%3BDDR2"></a>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/roguepc.wordpress.com/4/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/roguepc.wordpress.com/4/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/roguepc.wordpress.com/4/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/roguepc.wordpress.com/4/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/roguepc.wordpress.com/4/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=4&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://roguepc.wordpress.com/2007/03/22/an-explanation-of-ddr-versus-ddr2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6c37e4db064c08c845cdb67d95ccac9?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">roguepc</media:title>
		</media:content>
	</item>
		<item>
		<title>It begins.</title>
		<link>http://roguepc.wordpress.com/2007/03/22/hello-world/</link>
		<comments>http://roguepc.wordpress.com/2007/03/22/hello-world/#comments</comments>
		<pubDate>Thu, 22 Mar 2007 02:27:38 +0000</pubDate>
		<dc:creator>roguepc</dc:creator>
				<category><![CDATA[Site News]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[First post!<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=1&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>First post!</p>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/roguepc.wordpress.com/1/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/roguepc.wordpress.com/1/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/roguepc.wordpress.com/1/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/roguepc.wordpress.com/1/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/roguepc.wordpress.com/1/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=1&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://roguepc.wordpress.com/2007/03/22/hello-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6c37e4db064c08c845cdb67d95ccac9?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">roguepc</media:title>
		</media:content>
	</item>
		<item>
		<title>An explanation of CPU / Processor L2 Cache</title>
		<link>http://roguepc.wordpress.com/2007/03/21/an-explanation-of-cpu-processor-l2-cache/</link>
		<comments>http://roguepc.wordpress.com/2007/03/21/an-explanation-of-cpu-processor-l2-cache/#comments</comments>
		<pubDate>Thu, 22 Mar 2007 03:14:35 +0000</pubDate>
		<dc:creator>roguepc</dc:creator>
				<category><![CDATA[Technical Articles]]></category>

		<guid isPermaLink="false">http://roguepc.wordpress.com/2007/03/21/an-explanation-of-cpu-processor-l2-cache/</guid>
		<description><![CDATA[Article Technical Level: Novice This is a simplified quality explanation of CPU cache and how it works. Many folks wonder why some processors have very little cache and others have enormous amounts as well as how it works. Cache: The Athlon X2 has 2x 512KB cache allocations for L2 Cache. This is a very small [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=3&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Article Technical Level: <strong>Novice</strong></p>
<p>This is a simplified quality explanation of CPU cache and how it works.  Many folks wonder why some processors have very little cache and others have enormous amounts as well as how it works.</p>
<p>Cache: The Athlon X2 has 2x 512KB cache allocations for L2 Cache. This is a very small data block (memory) built directly into the CPU itself. This is very high speed memory (exponentially faster then RAM) used for storing each block of data to be processed by the CPU as it enters. There are several &#8220;levels&#8221; of cache which are related to how they connect to the CPU (hence L1, L2, etc). L2 Cache is almost always the quoted part of any processor detail. Cache is also faster/slower and bigger/smaller. Think of it like a road. A 2 lane road with a 35mph limit should move just as many cars as 1 lane road with a 70mph limit (obviously this makes traffic patterns simplified but, its an example). In this case, the Athlon X2&#8242;s cache is very fast (think 70mph limit) but cannot contain a lot of data at a time (1 lane). AMD actually has 2x 1MB L2 cache processors in their FX and Opteron lines. The difference in performance with double the cache for AMD&#8217;s line of processors was about 1% in almost every application yet increased costs significantly. From a totally different perspective, Intel&#8217;s older line of Pentium 4, Pentium D series processors had huge amounts of L2 cache (up to 4MB!), Intel did this in an attempt to make up for a failing architecture, a band-aid fix to increase performance, though marginally. AMD&#8217;s Athlon X2 line uses separate L2 cache for each processor core (dual-core) so it really has a full 1MB on board (2x 512KB). Intel&#8217;s new Core 2 Duo line starts at 2MB and goes up to 4MB with their higher end Core 2 Duo&#8217;s. More cache generally means better performance, but when dealing with cache &#8211; there is extreme diminishing returns, cost goes up incredibly quick and performance increases are minimal. When I say &#8220;performance&#8221; in relation to CPU cache &#8211; it generally translate to the end user as slightly faster access times when doing things like starting a program or opening a file as the first bits of data to crunch are quickly grabbed from the file system. In reality, the difference is going to be incredibly minimal as long as the CPU is not &#8220;data starved&#8221;. This is what happens with the very low end CPU&#8217;s from Intel (Celeron) and AMD (Sempron). They have very small L2 cache blocks and the CPU crunches the data faster then the L2 cache can call and store it, the CPU ends up idling; waiting on data. If you do want to go with a CPU with more cache, we can look at upgrading the CPU to a higher rated Athlon X2 with 2x 1MB L2 (I believe the 4400+ has 2x 1MB) or to a FX series AMD CPU. All in all, 2x 512KB is indeed not a smaller then average cache size. The first Intel Celeron chips had zero L2 cache.</p>
<a class="DiggThisButton DiggMedium" href="http://digg.com/submit?url=http%3A%2F%2Froguepc.wordpress.com%2F2007%2F03%2F21%2Fan-explanation-of-cpu-processor-l2-cache%2F&amp;title=An+explanation+of+CPU+%2F+Processor+L2%26nbsp%3BCache"></a>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/roguepc.wordpress.com/3/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/roguepc.wordpress.com/3/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/roguepc.wordpress.com/3/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/roguepc.wordpress.com/3/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/roguepc.wordpress.com/3/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=roguepc.wordpress.com&amp;blog=901776&amp;post=3&amp;subd=roguepc&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://roguepc.wordpress.com/2007/03/21/an-explanation-of-cpu-processor-l2-cache/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/d6c37e4db064c08c845cdb67d95ccac9?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">roguepc</media:title>
		</media:content>
	</item>
	</channel>
</rss>
