<?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; Garbage Collection</title>
	<atom:link href="http://blog.dynatrace.com/tag/garbage-collection/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>Thu, 29 Jul 2010 11:16:55 +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>Garbage Collection in IE7 heavily impacted by number of JavaScript objects and string sizes</title>
		<link>http://blog.dynatrace.com/2010/03/23/garbage-collection-in-ie7-heavily-impacted-by-number-of-javascript-objects-and-string-sizes/</link>
		<comments>http://blog.dynatrace.com/2010/03/23/garbage-collection-in-ie7-heavily-impacted-by-number-of-javascript-objects-and-string-sizes/#comments</comments>
		<pubDate>Tue, 23 Mar 2010 17:22:28 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[Architecture and Performance]]></category>
		<category><![CDATA[From the lab]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1806</guid>
		<description><![CDATA[
			
				
			
		
After my recent presentation at TSSJS &#8211; Performance Anti-Patterns in AJAX Applications - I got interesting feedback from one of the attendees: &#8220;The presentation was good but I thought you are talking more about actual problems with XHR/AJAX Requests&#8221;. I have to admit that I focused on all common problems of Web 2.0 applications &#8211; [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2010/03/23/garbage-collection-in-ie7-heavily-impacted-by-number-of-javascript-objects-and-string-sizes/feed/</wfw:commentRss>
		<slash:comments>6</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 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>Performance Analysis: Comparing Interactive and Low Latency GC Strategies in .NET</title>
		<link>http://blog.dynatrace.com/2009/04/13/performance-analysis-comparing-interactive-and-low-latency-gc-strategies-in-net/</link>
		<comments>http://blog.dynatrace.com/2009/04/13/performance-analysis-comparing-interactive-and-low-latency-gc-strategies-in-net/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 19:22:39 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=464</guid>
		<description><![CDATA[
			
				
			
		
The .NET Runtime can run with different GC flavors. The following article does a good job in explaining the options: Low Latency GC in .NET 3.5 by Sasha Goldshtein.
Comparing the two modi with a sample application
I was curious about how the different modi affect the time spent by the Garbage Collector. I therefore created a sample [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2009/04/13/performance-analysis-comparing-interactive-and-low-latency-gc-strategies-in-net/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Performance Analysis: Identify GC bottlenecks in distributed heterogeneous environments</title>
		<link>http://blog.dynatrace.com/2009/04/08/performance-analysis-identify-gc-bottlenecks-in-distributed-heterogeneous-environments/</link>
		<comments>http://blog.dynatrace.com/2009/04/08/performance-analysis-identify-gc-bottlenecks-in-distributed-heterogeneous-environments/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 11:36:13 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=456</guid>
		<description><![CDATA[
			
				
			
		
Garbage Collection can have a major impact on application performance. The more distributed an application becomes the trickier it is to identify the impact on the overall transaction response times. If you are dealing with heterogeneous systems it is even harder because the set of tools out there usually don&#8217;t cross runtime and technology boundaries.
Identifying [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2009/04/08/performance-analysis-identify-gc-bottlenecks-in-distributed-heterogeneous-environments/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Performance Analysis: How to identify &#8220;bad&#8221; methods messing up the GC</title>
		<link>http://blog.dynatrace.com/2009/04/07/performance-analysis-how-to-identify-bad-methods-messing-up-the-gc/</link>
		<comments>http://blog.dynatrace.com/2009/04/07/performance-analysis-how-to-identify-bad-methods-messing-up-the-gc/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 11:16:25 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Patterns and Practices]]></category>
		<category><![CDATA[Garbage Collection]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=434</guid>
		<description><![CDATA[
			
				
			
		
Whenever the Garbage Collector kicks in to free up memory - the runtime puts all currently executing threads on hold in order to do the cleanup. The GC runs when the application tries to allocate new objects and not enough free memory is available in the 1st Generation Heap. Putting the current execution on hold means [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2009/04/07/performance-analysis-how-to-identify-bad-methods-messing-up-the-gc/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>.NET Performance Analysis: A .NET Garbage Collection Mystery</title>
		<link>http://blog.dynatrace.com/2009/03/31/net-performance-analysis-a-net-garbage-collection-mystery/</link>
		<comments>http://blog.dynatrace.com/2009/03/31/net-performance-analysis-a-net-garbage-collection-mystery/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 18:20:11 +0000</pubDate>
		<dc:creator>Andreas Grabner</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Garbage Collection]]></category>

		<guid isPermaLink="false">http://blog.dynatrace.com/?p=421</guid>
		<description><![CDATA[
			
				
			
		
Memory Management in .NET is a broad topic with a lot of &#8220;mysteries&#8221; that come with it. Heavy memory usage as well as frequent allocations affect the performance of your application because lots of time is spent by the Garbage Collector to free up space in the individual Heap Generations.
Its a good practice to monitor [...]]]></description>
		<wfw:commentRss>http://blog.dynatrace.com/2009/03/31/net-performance-analysis-a-net-garbage-collection-mystery/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
