<?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>Chaotic Java &#187; Performance</title>
	<atom:link href="http://chaoticjava.com/posts/category/code/performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://chaoticjava.com</link>
	<description>The internet, design patterns, frameworks and Java</description>
	<lastBuildDate>Mon, 14 Nov 2011 03:49:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Java Logger Memory Leaks</title>
		<link>http://chaoticjava.com/posts/java-logger-memory-leaks/</link>
		<comments>http://chaoticjava.com/posts/java-logger-memory-leaks/#comments</comments>
		<pubDate>Sun, 05 Jul 2009 18:13:52 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[logger]]></category>
		<category><![CDATA[memory leak]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=292</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/java-logger-memory-leaks/";</script>Recently we switched from Log4J to the java.util.logger package (for this entry it will be called the &#8220;Java Logger&#8221;). Why, you might wonder, and I don&#8217;t have a good reason to give other than the illusion the Java Logger package gives as being more standard. I would like to stress the word illusion for a [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/java-logger-memory-leaks/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>IO performance &#8211; Tar vs. File vs. Byte streams</title>
		<link>http://chaoticjava.com/posts/io-performance-tar-file-bytes/</link>
		<comments>http://chaoticjava.com/posts/io-performance-tar-file-bytes/#comments</comments>
		<pubDate>Sat, 06 Dec 2008 23:12:48 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[io]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=240</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/io-performance-tar-file-bytes/";</script>One of the most classic patterns in software is the producer-consumer pattern. There is a module producing data, and a module reading it for further processing. Moreover, in order to achieve better performance, usually there are many consumer modules running on many different threads while the producer (or several producers) run on its own thread. [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/io-performance-tar-file-bytes/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>GC Tips and Memory Leaks</title>
		<link>http://chaoticjava.com/posts/gc-tips-and-memory-leaks/</link>
		<comments>http://chaoticjava.com/posts/gc-tips-and-memory-leaks/#comments</comments>
		<pubDate>Tue, 29 Jan 2008 10:00:51 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/posts/gc-tips-and-memory-leaks/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/gc-tips-and-memory-leaks/";</script>After the two posts about garbage collection (basic and advanced) I started receiving questions regarding the works of the GC, and tips on how to use it properly. This post will be devoted to that subject, with some of the questions asked brought into highlight and answered using a lot of information coming from a [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/gc-tips-and-memory-leaks/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>NIO &#8211; Data flow made resource-efficient</title>
		<link>http://chaoticjava.com/posts/nio-data-flow-made-resource-efficient/</link>
		<comments>http://chaoticjava.com/posts/nio-data-flow-made-resource-efficient/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 09:27:40 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/posts/nio-data-flow-made-resource-efficient/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/nio-data-flow-made-resource-efficient/";</script>This post is all about data flow in the â€œNew I/Oâ€ framework. The data flow mechanism in NIO is essentially different from the â€œoldâ€ IO. There are no decorators to data, and the entire framework revolves around getting one thing done, and done really well: transferring data from an external source into the application or [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/nio-data-flow-made-resource-efficient/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Parallel and concurrent garbage collectors</title>
		<link>http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/</link>
		<comments>http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 06:13:12 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/";</script>In the last post, Iâ€™ve been talking about the basics of garbage collection and the generational garbage collector. While the generational garbage collector brought huge performance benefits by getting the large, old generation memory area to be infrequently visited by the collector, it still wasnâ€™t enough for the new era of faster processors and memory [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>How does garbage collection work?</title>
		<link>http://chaoticjava.com/posts/how-does-garbage-collection-work/</link>
		<comments>http://chaoticjava.com/posts/how-does-garbage-collection-work/#comments</comments>
		<pubDate>Wed, 02 Jan 2008 06:05:19 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JVM]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/posts/how-does-garbage-collection-work/</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/how-does-garbage-collection-work/";</script>It seems to me that the importance of garbage collection in Java (and other garbage collected languages) is disproportional to the explanations given about it. While there would be millions of articles when you look for JavaFX examples, there would be only a couple if you tried to search about the â€œParallel Compacting Collectorâ€ mentioned [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/how-does-garbage-collection-work/feed/</wfw:commentRss>
		<slash:comments>63</slash:comments>
		</item>
		<item>
		<title>Autoboxing Tips</title>
		<link>http://chaoticjava.com/posts/autoboxing-tips/</link>
		<comments>http://chaoticjava.com/posts/autoboxing-tips/#comments</comments>
		<pubDate>Sun, 26 Feb 2006 22:21:49 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[Tiger]]></category>

		<guid isPermaLink="false">http://javachaos.crazyredpanda.com/?p=138</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/autoboxing-tips/";</script>Autoboxing, a feature which seems like it had squeezed into JSR 201, is a convenience feature which has its own bag of tricks. This feature seems to come as a complement to the major EoD feature in Tiger, Generics. Since generics can&#8217;t be used with primitives as their types (i.e. Can&#8217;t declare Collection&#60;int&#62;), their wrappers [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/autoboxing-tips/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>StringBuilder vs. String</title>
		<link>http://chaoticjava.com/posts/stringbuilder-vs-string/</link>
		<comments>http://chaoticjava.com/posts/stringbuilder-vs-string/#comments</comments>
		<pubDate>Thu, 16 Feb 2006 07:30:17 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Language]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://javachaos.crazyredpanda.com/?p=131</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/stringbuilder-vs-string/";</script>A lot has been said, written and blogged on this subject, I know. I&#8217;ll try to cover it from the disassembly angle, though, after going over the main points of this comparison. Why use StringBuilder? A good question deserves a good answer. See, the String class is an immutable class &#8211; It will never really [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/stringbuilder-vs-string/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The hardly known MessageFormat</title>
		<link>http://chaoticjava.com/posts/the-hardly-known-messageformat/</link>
		<comments>http://chaoticjava.com/posts/the-hardly-known-messageformat/#comments</comments>
		<pubDate>Thu, 09 Feb 2006 00:11:56 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://javachaos.crazyredpanda.com/?p=122</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/the-hardly-known-messageformat/";</script>I wonder how many people actually know about java.text.MessageFormat. I didn&#8217;t until a few days ago, and it&#8217;s a shame, in my opinion. In Java 5.0, we were introduced with a new feature which was the new String.format method, with the complimentary PrintStream.printf method (classically used via the System.out member). This feature allowed us to [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/the-hardly-known-messageformat/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

