<?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: Importance of parallel test environments</title>
	<atom:link href="http://www.fuzzylizard.com/archives/2007/03/19/873/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com/archives/2007/03/19/873/</link>
	<description>Web development and design with a little VFX thrown in for fun</description>
	<lastBuildDate>Fri, 14 Jan 2011 22:45:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: nard</title>
		<link>http://www.fuzzylizard.com/archives/2007/03/19/873/comment-page-1/#comment-11894</link>
		<dc:creator>nard</dc:creator>
		<pubDate>Fri, 23 Mar 2007 16:10:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2007/03/19/873/#comment-11894</guid>
		<description>yes, i&#039;ve experienced the same thing as you, since I just completed performance testing. although I ran into a different situation where we shared a load balancer with production lol. But parallel environments are quite expensive. especially if the qa environment is a parallel of production already and you need one for staging or performance testing.  I think the way to go is a virtualized environment for QA, and a staging environment that is the same specs/design as production for doing all the fun stuff. that way it does not interfere with QA trying to finish their testing cycles, and gives you a good idea how it will be like when it is deployed on production like hardware.

yea, i was also surprised at how slow webservices were when I was querying large datasets, but maybe i wasnt really doing it very smart in how i requested the information lol =p</description>
		<content:encoded><![CDATA[<p>yes, i&#8217;ve experienced the same thing as you, since I just completed performance testing. although I ran into a different situation where we shared a load balancer with production lol. But parallel environments are quite expensive. especially if the qa environment is a parallel of production already and you need one for staging or performance testing.  I think the way to go is a virtualized environment for QA, and a staging environment that is the same specs/design as production for doing all the fun stuff. that way it does not interfere with QA trying to finish their testing cycles, and gives you a good idea how it will be like when it is deployed on production like hardware.</p>
<p>yea, i was also surprised at how slow webservices were when I was querying large datasets, but maybe i wasnt really doing it very smart in how i requested the information lol =p</p>
]]></content:encoded>
	</item>
</channel>
</rss>

