<?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/"
	>

<channel>
	<title>Performance, Scalability and Architecture - Java and .NET Application Performance Management (dynaTrace Blog) &#187; Alois Reitbauer</title>
	<atom:link href="http://blog.dynatrace.com/author/alois-reitbauer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com</link>
	<description>dynaTrace Blog on Performance, Scalabilty and Architecture - Java and .NET  Application Performance Management</description>
	<lastBuildDate>Tue, 16 Mar 2010 12:50:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Week 6 &#8211; How to Make Developers Write Performance Tests</title>
		<link>http://blog.dynatrace.com/2010/03/11/week-6-how-to-make-developers-write-performance-tests/</link>
		<comments>http://blog.dynatrace.com/2010/03/11/week-6-how-to-make-developers-write-performance-tests/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 17:11:40 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Agile Performance]]></category>
		<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1754</guid>
		<description><![CDATA[
			
				
			
		
I had an interesting conversation with our Test Automation team lead Stefan – who Andi interviewed for our “Eating our own Dog Food ” article – on his experiences with the willingness of developers to write performance tests.
I asked a provocative question: do developers really want to write them in the first place? First he [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/03/11/week-6-how-to-make-developers-write-performance-tests/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Week 5 &#8211; Hunting Lost Treasures: Understanding and Finding Memory Leaks</title>
		<link>http://blog.dynatrace.com/2010/03/03/week-5-hunting-lost-treasures-understanding-and-finding-memory-leaks/</link>
		<comments>http://blog.dynatrace.com/2010/03/03/week-5-hunting-lost-treasures-understanding-and-finding-memory-leaks/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 09:58:34 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Monitoring]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1662</guid>
		<description><![CDATA[
			
				
			
		
Searching for memory leaks can easily become an adventure – fighting through a jungle of objects and references. When the leak occurs in production time is short and you have to act fast. Like in a treasure hunt, we have to interpret signs, unravel mysteries to finally find the “lost” memory.
Memory leaks – together with [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/03/03/week-5-hunting-lost-treasures-understanding-and-finding-memory-leaks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Low Hanging Fruits in Optimizing J EE Performance</title>
		<link>http://blog.dynatrace.com/2010/02/24/low-hanging-fruits-in-optimizing-j-ee-performance/</link>
		<comments>http://blog.dynatrace.com/2010/02/24/low-hanging-fruits-in-optimizing-j-ee-performance/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 11:55:24 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1636</guid>
		<description><![CDATA[
			
				
			
		


View more presentations from Alois Reitbauer.

// 

]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/02/24/low-hanging-fruits-in-optimizing-j-ee-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Selected readings for my JAX London Session</title>
		<link>http://blog.dynatrace.com/2010/02/22/selected-readings-for-my-jax-london-session/</link>
		<comments>http://blog.dynatrace.com/2010/02/22/selected-readings-for-my-jax-london-session/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 18:52:38 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Public Events]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1632</guid>
		<description><![CDATA[
			
				
			
		
Here you can find some selected material on performance related topics which I also covered in my talks at JAX London.
For a couple of performance related presentations I recommend to have a look at the slides of the Performance Workshop of W-JAX 2009. The cover a number of performance related topics from the technological basis [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/02/22/selected-readings-for-my-jax-london-session/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Week 4 &#8211; Why &#8220;top ten&#8221; Performance Reports are not the final answer</title>
		<link>http://blog.dynatrace.com/2010/02/18/week-4-why-top-ten-performance-reporsts-are-not-the-final-answer/</link>
		<comments>http://blog.dynatrace.com/2010/02/18/week-4-why-top-ten-performance-reporsts-are-not-the-final-answer/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 14:45:04 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Monitoring]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1573</guid>
		<description><![CDATA[
			
				
			
		
In this post I will address top ten reports and their usefulness in performance engineering. Regularly I hear people saying: “Can you show me the top ten database statements” or something similar. Their approach to performance engineering is to look at the slowest or most time-consuming statements and then make them faster. While this is [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/02/18/week-4-why-top-ten-performance-reporsts-are-not-the-final-answer/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Week 3 &#8211; Myths and Truths about Performance Measurement Overhead</title>
		<link>http://blog.dynatrace.com/2010/02/09/week-3-myths-and-truths-about-performance-measurement-overhead/</link>
		<comments>http://blog.dynatrace.com/2010/02/09/week-3-myths-and-truths-about-performance-measurement-overhead/#comments</comments>
		<pubDate>Tue, 09 Feb 2010 15:35:38 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1464</guid>
		<description><![CDATA[
			
				
			
		
In this third article of my Performance Almanac I discuss the role of overhead in performance management. As a performance management solution provider we’re  frequently asked  “How much overhead does your solution have?” This question is however a bit more complex to answer than just giving a single number.
When discussing this topic I [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/02/09/week-3-myths-and-truths-about-performance-measurement-overhead/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Week 2 &#8211; The many faces of end-user experience monitoring</title>
		<link>http://blog.dynatrace.com/2010/01/18/week-2-the-many-faces-of-end-user-experience-monitoring/</link>
		<comments>http://blog.dynatrace.com/2010/01/18/week-2-the-many-faces-of-end-user-experience-monitoring/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 10:17:45 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1349</guid>
		<description><![CDATA[
			
				
			
		
Inspired by a comment of Wim Leers on one of our other posts on web performance, I decided to switch plans and write this week about end-user experience monitoring. If you google end-user experience monitoring you will find a number of different approaches.
End- user experience &#8211; as I think we all agree &#8211; is the [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/01/18/week-2-the-many-faces-of-end-user-experience-monitoring/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>dynaTrace Application Performance Almanac 2010</title>
		<link>http://blog.dynatrace.com/2010/01/12/dynatrace-application-performance-almanach-2010/</link>
		<comments>http://blog.dynatrace.com/2010/01/12/dynatrace-application-performance-almanach-2010/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 09:15:39 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1314</guid>
		<description><![CDATA[
			
				
			
		
Inspired by the work of Stoyan on his performance advent calendar I decided to start an application performance almanac. According to wikipedia an alamanac is -&#8221;&#8230; an annual publication containing information in a particular field&#8221;.
Throughout the year I will write weekly posts on a specific topic in the area of performance management. I have chosen this domain [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/01/12/dynatrace-application-performance-almanach-2010/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Week 1 &#8211; The Proactivity of Troubleshooting</title>
		<link>http://blog.dynatrace.com/2010/01/12/week-1-the-proactivity-of-troubleshooting/</link>
		<comments>http://blog.dynatrace.com/2010/01/12/week-1-the-proactivity-of-troubleshooting/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 09:09:33 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1317</guid>
		<description><![CDATA[
			
				
			
		
Troubleshooting of performance problems is very often &#8211; if not almost always &#8211; viewed as a reactive activity. Frankly, I have often seen it done in such a reactive as a firefight; however effective troubleshooting should build upon a solid diagnostics process. If you handle troubleshooting as if firefighting rather than based on solid diagnosis, [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/01/12/week-1-the-proactivity-of-troubleshooting/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Future of Testcenters (in German)</title>
		<link>http://blog.dynatrace.com/2010/01/05/the-future-of-testcenters-in-german/</link>
		<comments>http://blog.dynatrace.com/2010/01/05/the-future-of-testcenters-in-german/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 12:38:45 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1298</guid>
		<description><![CDATA[
			
				
			
		
dynaTrace CTO and Founder Bernd Greifeneder talking about the future of Testcenters. Will test centers as we know them fade away? What are the drivers for changes and  how should test centers react to them?
]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/01/05/the-future-of-testcenters-in-german/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
