<?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>Application Performance, Scalability and Architecture – The dynaTrace Blog &#187; Performance Almanac</title>
	<atom:link href="http://blog.dynatrace.com/tag/performance-almanac/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 09:03:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Web Performance Optimization Use Cases – Part 3 Automation</title>
		<link>http://blog.dynatrace.com/2010/10/30/web-performance-optimization-use-cases-part-3-automation/</link>
		<comments>http://blog.dynatrace.com/2010/10/30/web-performance-optimization-use-cases-part-3-automation/#comments</comments>
		<pubDate>Sat, 30 Oct 2010 17:48:44 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2591</guid>
		<description><![CDATA[In the first and second post of this series I discussed benchmarking and different approaches towards optimization of web application. As already mentioned in the last post, as soon as you get used to working with Key Performance Indicators you will want to automatically monitor them. ShowSlow is a great example of how you can [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/10/30/web-performance-optimization-use-cases-part-3-automation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Web Performance Optimization Use Cases – Part 2 Optimization</title>
		<link>http://blog.dynatrace.com/2010/10/12/web-performance-optimization-use-cases-part-2-optimization/</link>
		<comments>http://blog.dynatrace.com/2010/10/12/web-performance-optimization-use-cases-part-2-optimization/#comments</comments>
		<pubDate>Tue, 12 Oct 2010 23:26:52 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[JavaScript/AJAX]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2578</guid>
		<description><![CDATA[In the last post I discussed benchmarking as the first use case for Web Performance Optimization (WPO). This time I will take a closer look at optimization. After we have discovered how our site behaves compared to our competition – or any reference we might want to benchmark against – we want to learn how [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/10/12/web-performance-optimization-use-cases-part-2-optimization/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Performance Optimization Use Cases – Part 1 Benchmarking</title>
		<link>http://blog.dynatrace.com/2010/09/28/web-performance-optimization-use-cases-part-1-benchmarking/</link>
		<comments>http://blog.dynatrace.com/2010/09/28/web-performance-optimization-use-cases-part-1-benchmarking/#comments</comments>
		<pubDate>Tue, 28 Sep 2010 22:04:43 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[JavaScript/AJAX]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2555</guid>
		<description><![CDATA[Web Performance Optimization (WPO) constitutes of a set of activities targeted at improving the performance of web applications. First coined by Steve Souders WPO is developing into a growing industry. Every month new companies and projects offering web performance services emerge. WPO is much more than performance analysis; however, performance analysis is a central part [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/09/28/web-performance-optimization-use-cases-part-1-benchmarking/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Week 38 &#8211; Transactions in a JPA World</title>
		<link>http://blog.dynatrace.com/2010/09/14/week-38-transactions-in-a-jpa-world/</link>
		<comments>http://blog.dynatrace.com/2010/09/14/week-38-transactions-in-a-jpa-world/#comments</comments>
		<pubDate>Tue, 14 Sep 2010 01:17:08 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[Hibernate]]></category>
		<category><![CDATA[JPA]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2517</guid>
		<description><![CDATA[The use of transactions is a cornerstone when building database applications. However in our daily work, we often do not really care much about them. In many cases they are handled implicitly for us by the (J EE) container or application framework – such as Spring &#8211; we are using. We rely on these frameworks [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/09/14/week-38-transactions-in-a-jpa-world/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Week 23 &#8211; 7 Rules to Improve your Application Performance Practices</title>
		<link>http://blog.dynatrace.com/2010/06/17/week-23-7-rules-to-improve-your-application-performance-practices/</link>
		<comments>http://blog.dynatrace.com/2010/06/17/week-23-7-rules-to-improve-your-application-performance-practices/#comments</comments>
		<pubDate>Thu, 17 Jun 2010 07:41:27 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2265</guid>
		<description><![CDATA[In this post I discuss the seven most important steps to improve your application performance practices. These simple-to-follow practices will help you to improve the way you deal with application performance. Besides eventually improving the performance of your applications it will help you to avoid playing the classical blame game which normally happens when something [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/06/17/week-23-7-rules-to-improve-your-application-performance-practices/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Week 16 &#8211; Who is to blame for bad application performance?</title>
		<link>http://blog.dynatrace.com/2010/05/28/week-16-who-is-to-blame-for-bad-application-performance/</link>
		<comments>http://blog.dynatrace.com/2010/05/28/week-16-who-is-to-blame-for-bad-application-performance/#comments</comments>
		<pubDate>Fri, 28 May 2010 13:42:50 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2213</guid>
		<description><![CDATA[When something goes wrong who’s to blame? In this post I take a closer look at who is responsible when applications have performance problems. Interestingly very often the question as to who is responsible is at least as important as how to solve the problem. In order to not have to search for the responsible [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/05/28/week-16-who-is-to-blame-for-bad-application-performance/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Week 22 &#8211; Is There a Business Case for Application Performance?</title>
		<link>http://blog.dynatrace.com/2010/05/26/week-22-is-there-a-business-case-for-application-performance/</link>
		<comments>http://blog.dynatrace.com/2010/05/26/week-22-is-there-a-business-case-for-application-performance/#comments</comments>
		<pubDate>Wed, 26 May 2010 11:45:32 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2196</guid>
		<description><![CDATA[We all know that slow performance – and service disruption even more – affects our business services and eventually our revenue. At the same time we say that major parts of companies are not willing to invest in performance. In this post I will discuss why we find ourselves in this paradox and how to [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/05/26/week-22-is-there-a-business-case-for-application-performance/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Week 14 &#8211; Building Your Own Amazon CloudWatch Monitor in 5 Steps</title>
		<link>http://blog.dynatrace.com/2010/04/22/week-14-building-your-own-amazon-cloudwatch-monitor-in-5-steps/</link>
		<comments>http://blog.dynatrace.com/2010/04/22/week-14-building-your-own-amazon-cloudwatch-monitor-in-5-steps/#comments</comments>
		<pubDate>Thu, 22 Apr 2010 14:23:46 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Virtualization/Cloud]]></category>
		<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2070</guid>
		<description><![CDATA[Amazon EC2 offers the CloudWatch service to monitor cloud instances as well as load balancers. While this service comes at some cost (0,015$/hour/instance) it offers useful infrastructure metrics about the performance of your EC2 infrastructure. While there are commercial and free tools out there which provide this service, you might not want to invest in [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/04/22/week-14-building-your-own-amazon-cloudwatch-monitor-in-5-steps/feed/</wfw:commentRss>
		<slash:comments>71</slash:comments>
		</item>
		<item>
		<title>Week 15 &#8211; Optimizing Data Intensive Web Pages by Example</title>
		<link>http://blog.dynatrace.com/2010/04/14/week-15-optimizing-data-intensive-webpages-by-example/</link>
		<comments>http://blog.dynatrace.com/2010/04/14/week-15-optimizing-data-intensive-webpages-by-example/#comments</comments>
		<pubDate>Wed, 14 Apr 2010 15:55:30 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[JavaScript/AJAX]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1928</guid>
		<description><![CDATA[Lately I was checking out ShowSlow. The site is really great. It combines YSlow and PageSpeed metrics and visualizes them in a really nice way. When I clicked on the URLs Measured Tab I had to wait quite some time until the page finished downloading. While this page is really displaying a lot of information, [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/04/14/week-15-optimizing-data-intensive-webpages-by-example/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Week 8 &#8211; Challenges in Tracing JavaScript Performance by Example</title>
		<link>http://blog.dynatrace.com/2010/04/09/week-8-challenges-in-tracing-javascript-performance-by-example/</link>
		<comments>http://blog.dynatrace.com/2010/04/09/week-8-challenges-in-tracing-javascript-performance-by-example/#comments</comments>
		<pubDate>Fri, 09 Apr 2010 11:28:27 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[JavaScript/AJAX]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Performance Almanac]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1938</guid>
		<description><![CDATA[In an earlier post I already discussed several approaches towards end-user experience (or performance) monitoring including their pros and cons. In this post I will present a simple real-world sample which shows the limits of performance traceability in AJAX applications. As I don’t like Hello World samples, I thought I’d rather build something a bit [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/04/09/week-8-challenges-in-tracing-javascript-performance-by-example/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

