<?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: A Million Reasons Why</title>
	<atom:link href="http://blogs.amd.com/work/2009/04/06/a-million-reasons-why/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.amd.com/work/2009/04/06/a-million-reasons-why/</link>
	<description></description>
	<lastBuildDate>Mon, 19 Oct 2009 15:00:18 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Curtis Hart</title>
		<link>http://blogs.amd.com/work/2009/04/06/a-million-reasons-why/comment-page-1/#comment-27</link>
		<dc:creator>Curtis Hart</dc:creator>
		<pubDate>Tue, 07 Apr 2009 20:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.amd.com/work/?p=167#comment-27</guid>
		<description>This is great for SMB virtualization and software  development as well.  We use agile methodology and a continuous integration development environment. In other words, we push code to the servers all the time.  Also we have about 90% code coverage with our automated testing.

Our current environment for one project looks like this:

4 Demo servers
1 Acceptance server
1 Building server
1 Regression test

We have 2-3 boxes, demo servers can&#039;t slow down because of the IO on the on Acceptance, Build, and Test. Additionally, we have to have fall over protection (no way around that). 

With this kind of set up, we could reduce our server space without worrying about the client experience suffering.  This scenario could really save us some money on server room lease space. We could decrease from 3-4 load balanced boxes to 2, and out-perform what we have now.</description>
		<content:encoded><![CDATA[<p>This is great for SMB virtualization and software  development as well.  We use agile methodology and a continuous integration development environment. In other words, we push code to the servers all the time.  Also we have about 90% code coverage with our automated testing.</p>
<p>Our current environment for one project looks like this:</p>
<p>4 Demo servers<br />
1 Acceptance server<br />
1 Building server<br />
1 Regression test</p>
<p>We have 2-3 boxes, demo servers can&#8217;t slow down because of the IO on the on Acceptance, Build, and Test. Additionally, we have to have fall over protection (no way around that). </p>
<p>With this kind of set up, we could reduce our server space without worrying about the client experience suffering.  This scenario could really save us some money on server room lease space. We could decrease from 3-4 load balanced boxes to 2, and out-perform what we have now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Z</title>
		<link>http://blogs.amd.com/work/2009/04/06/a-million-reasons-why/comment-page-1/#comment-25</link>
		<dc:creator>Z</dc:creator>
		<pubDate>Mon, 06 Apr 2009 19:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.amd.com/work/?p=167#comment-25</guid>
		<description>Perfect fit for ZFS L2ARC... Now that HP supports Solaris</description>
		<content:encoded><![CDATA[<p>Perfect fit for ZFS L2ARC&#8230; Now that HP supports Solaris</p>
]]></content:encoded>
	</item>
</channel>
</rss>
