<?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; Memory</title>
	<atom:link href="http://blog.dynatrace.com/tag/memory/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 10:35:01 +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>The Top Java Memory Problems &#8211; Part 2</title>
		<link>http://blog.dynatrace.com/2011/12/15/the-top-java-memory-problems-part-2/</link>
		<comments>http://blog.dynatrace.com/2011/12/15/the-top-java-memory-problems-part-2/#comments</comments>
		<pubDate>Thu, 15 Dec 2011 15:06:00 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[tuning]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3433</guid>
		<description><![CDATA[Some time back I planned to publish a series about java memory problems. It took me longer than originally planned, but here is the second installment. In the first part I talked about the different causes for memory leaks, but memory leaks are by far not the only issue around java memory management. Edit: A [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/12/15/the-top-java-memory-problems-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Object Caches need to be Memory-sensitive &#8211; Guest Blog by Christopher André</title>
		<link>http://blog.dynatrace.com/2011/05/17/why-object-caches-need-to-be-memory-sensitive-guest-blog-by-christopher-andre/</link>
		<comments>http://blog.dynatrace.com/2011/05/17/why-object-caches-need-to-be-memory-sensitive-guest-blog-by-christopher-andre/#comments</comments>
		<pubDate>Tue, 17 May 2011 07:42:36 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Memory]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3680</guid>
		<description><![CDATA[Christopher André is an Enablement Service Consultant at dynaTrace and helps our Customers to maximize their value they get out of dynaTrace. The other day, I went to a customer who was experiencing a problem that happens quite frequently: he had a cache that was constantly growing, leading to OutOfMemory Exceptions. Other problems in the [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/05/17/why-object-caches-need-to-be-memory-sensitive-guest-blog-by-christopher-andre/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How Garbage Collection differs in the three big JVMs</title>
		<link>http://blog.dynatrace.com/2011/05/11/how-garbage-collection-differs-in-the-three-big-jvms/</link>
		<comments>http://blog.dynatrace.com/2011/05/11/how-garbage-collection-differs-in-the-three-big-jvms/#comments</comments>
		<pubDate>Wed, 11 May 2011 05:03:02 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3645</guid>
		<description><![CDATA[Most articles about Garbage Collection ignore the fact that the Sun Hotspot JVM is not the only game in town. In fact whenever you have to work with either IBM WebSphere or Oracle WebLogic you will run on a different runtime. While the concept of Garbage Collection is the same, the implementation is not and [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/05/11/how-garbage-collection-differs-in-the-three-big-jvms/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>Field Report &#8211; Application Performance Management in WebSphere Environments</title>
		<link>http://blog.dynatrace.com/2011/05/10/field-report-application-performance-management-in-websphere-environments/</link>
		<comments>http://blog.dynatrace.com/2011/05/10/field-report-application-performance-management-in-websphere-environments/#comments</comments>
		<pubDate>Tue, 10 May 2011 06:43:40 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Database]]></category>
		<category><![CDATA[devops]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Production]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3590</guid>
		<description><![CDATA[Just in time for the upcoming Webinar with The BonTon Stores, were we talk about the challenges in operating complex WebSphere environments, we had another set of prospects running their applications on WebSphere. Francis Cordon, a colleague of mine, shares some of the screenshots resulting from these engagements. In this blog I want to highlight [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/05/10/field-report-application-performance-management-in-websphere-environments/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Top Java Memory Problems &#8211; Part 1</title>
		<link>http://blog.dynatrace.com/2011/04/20/the-top-java-memory-problems-part-1/</link>
		<comments>http://blog.dynatrace.com/2011/04/20/the-top-java-memory-problems-part-1/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 04:12:15 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3416</guid>
		<description><![CDATA[Memory and Garbage Collection problems are still the most prominent issues in any java application. One of the reasons is that the very nature of Garbage Collection is often misunderstood. This prompted me to write a summary of some of the most frequent and also most obscure memory related issues that I have encountered in [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/04/20/the-top-java-memory-problems-part-1/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Memory Leak Detection in Production &#8211; a Field Report</title>
		<link>http://blog.dynatrace.com/2011/04/08/memory-leak-detection-in-production-a-field-report/</link>
		<comments>http://blog.dynatrace.com/2011/04/08/memory-leak-detection-in-production-a-field-report/#comments</comments>
		<pubDate>Fri, 08 Apr 2011 05:26:10 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Memory]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3386</guid>
		<description><![CDATA[Memory Leaks are painful – especially when they crash your production servers. But &#8211; how does one go about analyzing the leak that only happens in the production environment? Here is a story I was told while on-site with one of our clients. I asked: “Chris, tell me about a recent performance problem and how [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/04/08/memory-leak-detection-in-production-a-field-report/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The impact of Garbage Collection on Java performance</title>
		<link>http://blog.dynatrace.com/2011/03/24/the-impact-of-garbage-collection-on-java-performance/</link>
		<comments>http://blog.dynatrace.com/2011/03/24/the-impact-of-garbage-collection-on-java-performance/#comments</comments>
		<pubDate>Thu, 24 Mar 2011 12:43:40 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[BestPractice]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=3062</guid>
		<description><![CDATA[In my last post I explained what a major Garbage Collection is. While a major Collection certainly has a negative impact on performance it is not the only thing that we need to watch out for. And in case of the CMS we might not always be able to distinguish between major and minor GC. [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/03/24/the-impact-of-garbage-collection-on-java-performance/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Major GCs &#8211; Separating Myth from Reality</title>
		<link>http://blog.dynatrace.com/2011/03/10/major-gcs-separating-myth-from-reality/</link>
		<comments>http://blog.dynatrace.com/2011/03/10/major-gcs-separating-myth-from-reality/#comments</comments>
		<pubDate>Thu, 10 Mar 2011 11:39:35 +0000</pubDate>
		<dc:creator>Michael Kopp</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Memory]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=2876</guid>
		<description><![CDATA[In a recent post we have shown how the Java Garbage Collection MXBean Counters have changed for the Concurrent Mark-and-Sweep Collector. It now reports all GC runs instead of just major collections. That prompted me to think about what a major GC actually is or what it should be. It is actually quite hard to find [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2011/03/10/major-gcs-separating-myth-from-reality/feed/</wfw:commentRss>
		<slash:comments>7</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 11: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>
		<category><![CDATA[Performance Almanac]]></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 [...]]]></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>1</slash:comments>
		</item>
		<item>
		<title>Java Memory Problems</title>
		<link>http://blog.dynatrace.com/2009/08/13/java-memory-problems/</link>
		<comments>http://blog.dynatrace.com/2009/08/13/java-memory-problems/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 12:44:34 +0000</pubDate>
		<dc:creator>Alois Reitbauer</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Memory]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=724</guid>
		<description><![CDATA[Memory Leaks and other memory related problems are among the most prominent performance and scalability problems in Java.  Reason enough to discuss this topic in more detail. The Java memory model- or more specifically the garbage collector &#8211;  has solved many memory problems. At the same time new ones have been created. Especially in J [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2009/08/13/java-memory-problems/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
	</channel>
</rss>

