<?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>Java Code Geeks &#187; Peter Lawrey</title> <atom:link href="http://www.javacodegeeks.com/author/Peter-Lawrey/feed" rel="self" type="application/rss+xml" /><link>http://www.javacodegeeks.com</link> <description>Java 2 Java Developers Resource Center</description> <lastBuildDate>Fri, 24 May 2013 13:00:38 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.5.1</generator> <item><title>Why a synchronized StringBuffer was never a good idea</title><link>http://www.javacodegeeks.com/2013/04/why-a-synchronized-stringbuffer-was-never-a-good-idea.html</link> <comments>http://www.javacodegeeks.com/2013/04/why-a-synchronized-stringbuffer-was-never-a-good-idea.html#comments</comments> <pubDate>Fri, 26 Apr 2013 19:00:38 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Core Java]]></category> <category><![CDATA[Concurrency]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=11913</guid> <description><![CDATA[Introduction StringBuffer is a synchronized class for mutable strings.  The main problem with making it synchronized is that It was usually used as a local variable so making it synchronized just made it slower. It was never a good idea to use it in a multi-threaded way.  This problem is that developers assumed that methods [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/04/why-a-synchronized-stringbuffer-was-never-a-good-idea.html/feed</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Lies, statistics and vendors</title><link>http://www.javacodegeeks.com/2013/04/lies-statistics-and-vendors-2.html</link> <comments>http://www.javacodegeeks.com/2013/04/lies-statistics-and-vendors-2.html#comments</comments> <pubDate>Thu, 04 Apr 2013 19:00:43 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Software Development]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=10761</guid> <description><![CDATA[Overview Reading performance results supplied by vendors is a skill in itself.   It can be difficult to compare numbers from different vendors on a fair basis, and even more difficult to estimate how a product will behave in your system. Lies and statistics One of the few quotes from University I remember goes roughly like this: [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/04/lies-statistics-and-vendors-2.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Chronicle and the Micro-Cloud</title><link>http://www.javacodegeeks.com/2013/02/chronicle-and-the-micro-cloud.html</link> <comments>http://www.javacodegeeks.com/2013/02/chronicle-and-the-micro-cloud.html#comments</comments> <pubDate>Thu, 28 Feb 2013 11:00:02 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Core Java]]></category> <category><![CDATA[Cloud]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=9183</guid> <description><![CDATA[Overview A common question I face is; how do you scale a Chronicle based system if it is single writer, multiple readers. While there are solutions to this problem, it is far more likely it won&#8217;t be a problem at all. The Micro-Cloud This is the term I have been using to describe a single [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/02/chronicle-and-the-micro-cloud.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Java is dead (again)</title><link>http://www.javacodegeeks.com/2013/02/java-is-dead-again.html</link> <comments>http://www.javacodegeeks.com/2013/02/java-is-dead-again.html#comments</comments> <pubDate>Tue, 19 Feb 2013 08:00:08 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Software Development]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=8807</guid> <description><![CDATA[Here is a couple of responses to this annual question I thought worth sharing: The Day Java lost the Battle There is a common myth amongst technologists that better technology will always be the most successful or that you must keep improving or die. A counter example I use is the QWERTY keyboard. No one [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/02/java-is-dead-again.html/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>A down side of durable messaging</title><link>http://www.javacodegeeks.com/2013/02/a-down-side-of-durable-messaging.html</link> <comments>http://www.javacodegeeks.com/2013/02/a-down-side-of-durable-messaging.html#comments</comments> <pubDate>Mon, 11 Feb 2013 20:00:42 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Software Development]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=8419</guid> <description><![CDATA[Overview Durable messaging can be very fast, as fast as non-durable messaging up to a point. Limitations of durable messaging Durable messaging is dependant on the size of your main memory and the speed of your hard drive.  If you have a HDD, this can be as low as 20 MB/s and as high as [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/02/a-down-side-of-durable-messaging.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>High Performance Durable Messaging</title><link>http://www.javacodegeeks.com/2013/02/high-performance-durable-messaging.html</link> <comments>http://www.javacodegeeks.com/2013/02/high-performance-durable-messaging.html#comments</comments> <pubDate>Mon, 04 Feb 2013 11:00:56 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Enterprise Java]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=8033</guid> <description><![CDATA[Overview While there are a good number of high performance messaging systems available for Java, most avoid quoting benchmarks which include durable messaging and serialization/deserialization of messages. This is done for a number of reasons; 1) you don&#8217;t always need or want durable messages 2) you want the option of using your own serialization. One [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/02/high-performance-durable-messaging.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Java Memory Model and optimisation</title><link>http://www.javacodegeeks.com/2013/01/java-memory-model-and-optimisation-2.html</link> <comments>http://www.javacodegeeks.com/2013/01/java-memory-model-and-optimisation-2.html#comments</comments> <pubDate>Fri, 25 Jan 2013 20:00:41 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Core Java]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=7628</guid> <description><![CDATA[Overview Many developers of multi-threaded code are familiar with the idea that different threads can have a different view of a value they are holding, this not the only reason a thread might not see a change if it is not made thread safe. The JIT itself can play a part. Why do different threads [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/01/java-memory-model-and-optimisation-2.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Should Java be more high level or low level?</title><link>http://www.javacodegeeks.com/2013/01/should-java-be-more-high-level-or-low-level.html</link> <comments>http://www.javacodegeeks.com/2013/01/should-java-be-more-high-level-or-low-level.html#comments</comments> <pubDate>Thu, 10 Jan 2013 14:00:27 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Core Java]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=6772</guid> <description><![CDATA[Overview Java 8 is bringing much antisipated features such as Lambda expressions, Type Annotations and Virtual Extensions. While this functionality is a) valuable, b) playing catch up with cooler languages, are these richer, higher level functionality the only area Java should be focused. &#160; &#160; &#160; &#160; &#160; What are the most widely used languages There [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2013/01/should-java-be-more-high-level-or-low-level.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Local variables inside a loop and performance</title><link>http://www.javacodegeeks.com/2012/12/local-variables-inside-a-loop-and-performance.html</link> <comments>http://www.javacodegeeks.com/2012/12/local-variables-inside-a-loop-and-performance.html#comments</comments> <pubDate>Tue, 25 Dec 2012 20:00:27 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Core Java]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=6115</guid> <description><![CDATA[Overview Sometimes a question comes up about how much work allocating a new local variable takes.  My feeling has always been that the code becomes optimised to the point where this cost is static i.e. done once, not each time the code is run. Recently Ishwor Gurung suggested considering moving some local variables outside a [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/12/local-variables-inside-a-loop-and-performance.html/feed</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Can synchronization be optimised away?</title><link>http://www.javacodegeeks.com/2012/12/can-synchronization-be-optimised-away.html</link> <comments>http://www.javacodegeeks.com/2012/12/can-synchronization-be-optimised-away.html#comments</comments> <pubDate>Mon, 24 Dec 2012 20:00:09 +0000</pubDate> <dc:creator>Peter Lawrey</dc:creator> <category><![CDATA[Java]]></category> <category><![CDATA[Concurrency]]></category><guid isPermaLink="false">http://www.javacodegeeks.com/?p=6078</guid> <description><![CDATA[Overview There is a common misconception that because the JIT is smart and synchronization can be eliminated for an object which is only local to a method that there is no performance impact. &#160; &#160; &#160; &#160; &#160; &#160; A test comparing StringBuffer and StringBuilder These two classes do basically the same thing except one [...]]]></description> <wfw:commentRss>http://www.javacodegeeks.com/2012/12/can-synchronization-be-optimised-away.html/feed</wfw:commentRss> <slash:comments>3</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 2/4 queries in 0.001 seconds using apc
Object Caching 1097/1098 objects using apc
Content Delivery Network via jcg.javacodegeeks.netdna-cdn.com

Served from: www.javacodegeeks.com @ 2013-05-24 18:20:52 -->