<?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: Performance testing &#8211; buried by an avalanche</title>
	<atom:link href="http://watchitlater.com/blog/2008/04/performance-testing-buried-by-an-avalanche/feed/" rel="self" type="application/rss+xml" />
	<link>http://watchitlater.com/blog/2008/04/performance-testing-buried-by-an-avalanche/</link>
	<description>A reluctant foray into the world of blogging.</description>
	<lastBuildDate>Thu, 17 May 2012 02:38:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Tom</title>
		<link>http://watchitlater.com/blog/2008/04/performance-testing-buried-by-an-avalanche/comment-page-1/#comment-1019</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 01 Jul 2008 16:12:59 +0000</pubDate>
		<guid isPermaLink="false">http://watchitlater.com/blog/?p=8#comment-1019</guid>
		<description>JMeter is a good tool, but the problem in my experience is that it is still possible to stop JMeter from sending requests by asking it to do things like large file uploads, thus blocking each thread. It is only an edge case, but when doing destructive testing, you really want to keep on sending requests, no matter what the state of the server is.

I know that I&#039;m being really pedantic here, but the blocking calls made by JMeter trouble me, as does scaling up using threads. Nervertheless I&#039;ll keep on using Grinder and JMeter till I stop being distracted by shiny things and finish off Thumper.</description>
		<content:encoded><![CDATA[<p>JMeter is a good tool, but the problem in my experience is that it is still possible to stop JMeter from sending requests by asking it to do things like large file uploads, thus blocking each thread. It is only an edge case, but when doing destructive testing, you really want to keep on sending requests, no matter what the state of the server is.</p>
<p>I know that I&#8217;m being really pedantic here, but the blocking calls made by JMeter trouble me, as does scaling up using threads. Nervertheless I&#8217;ll keep on using Grinder and JMeter till I stop being distracted by shiny things and finish off Thumper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernd Eckenfels</title>
		<link>http://watchitlater.com/blog/2008/04/performance-testing-buried-by-an-avalanche/comment-page-1/#comment-1014</link>
		<dc:creator>Bernd Eckenfels</dc:creator>
		<pubDate>Tue, 01 Jul 2008 02:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://watchitlater.com/blog/?p=8#comment-1014</guid>
		<description>Apache JMeter has a constant rate time. However it wont back-off. But you can size the thread pool accordingly, so you will never get more parallel requests than threads configured. Since the fixed-rate timer cant sleep negative time, its quite safe...

Bernd</description>
		<content:encoded><![CDATA[<p>Apache JMeter has a constant rate time. However it wont back-off. But you can size the thread pool accordingly, so you will never get more parallel requests than threads configured. Since the fixed-rate timer cant sleep negative time, its quite safe&#8230;</p>
<p>Bernd</p>
]]></content:encoded>
	</item>
</channel>
</rss>

