<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Quick initial Shark JIT on ARM benchmark</title>
	<atom:link href="http://labb.zafena.se/?feed=rss2&#038;p=282" rel="self" type="application/rss+xml" />
	<link>http://labb.zafena.se/?p=282</link>
	<description></description>
	<pubDate>Wed, 08 Sep 2010 23:25:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Damon Hart-Davis</title>
		<link>http://labb.zafena.se/?p=282#comment-5081</link>
		<dc:creator>Damon Hart-Davis</dc:creator>
		<pubDate>Thu, 05 Nov 2009 16:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://labb.zafena.se/?p=282#comment-5081</guid>
		<description>Testing started... Please fit protecting clothing and retreat to underground bunkers!  B^&#62;

Rgds

Damon</description>
		<content:encoded><![CDATA[<p>Testing started&#8230; Please fit protecting clothing and retreat to underground bunkers!  B^&gt;</p>
<p>Rgds</p>
<p>Damon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xerxes</title>
		<link>http://labb.zafena.se/?p=282#comment-5080</link>
		<dc:creator>xerxes</dc:creator>
		<pubDate>Thu, 05 Nov 2009 16:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://labb.zafena.se/?p=282#comment-5080</guid>
		<description>I can happily announce that the warm-uptime that i have been worried about have been all removed by combining the Shark JIT with the optimized ASM interpreter on ARM.
Edward Nevill are the one to thank that have made all this happen quite quickly, all sources can be found in the icedtea6 sourcetree and mailinglist.

I have made some armv5 binarys that can be run on Ubuntu Jaunty systems like the Sheeva Plug and OpenRD-Client.
Give it a spin and tell us what you think!
http://labb.zafena.se/shark-testing/armv5/

Cheers and thanks Ed!
Xerxes</description>
		<content:encoded><![CDATA[<p>I can happily announce that the warm-uptime that i have been worried about have been all removed by combining the Shark JIT with the optimized ASM interpreter on ARM.<br />
Edward Nevill are the one to thank that have made all this happen quite quickly, all sources can be found in the icedtea6 sourcetree and mailinglist.</p>
<p>I have made some armv5 binarys that can be run on Ubuntu Jaunty systems like the Sheeva Plug and OpenRD-Client.<br />
Give it a spin and tell us what you think!<br />
<a href="http://labb.zafena.se/shark-testing/armv5/" rel="nofollow">http://labb.zafena.se/shark-testing/armv5/</a></p>
<p>Cheers and thanks Ed!<br />
Xerxes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damon Hart-Davis</title>
		<link>http://labb.zafena.se/?p=282#comment-4894</link>
		<dc:creator>Damon Hart-Davis</dc:creator>
		<pubDate>Sat, 10 Oct 2009 20:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://labb.zafena.se/?p=282#comment-4894</guid>
		<description>As to optimising start-up...  The tiered compilation stuff that Steve Goldman of Sun was working on would of course help with that if you got a light C1 quickly and then C2 when needed:

http://blogs.sun.com/fatcatair/category/Java

But also I'd suggested to him to simply remember which methods had been hot at startup but didn't run long enough after being compiled to get much benefit from compilation.  On a subsequent run those would be compiled as soon as (and this before) they were called (C1 level I guess) like an old-fashioned JIT.

Much safer and less data and dependencies to store than a code cache, and the worst that can really happen is some excess compilation for things that turned out not to be early/start-up hotspots *this* time, eg because the code was changed.

Java could really benefit from having such work folded back in IMHO...

Rgds

Damon</description>
		<content:encoded><![CDATA[<p>As to optimising start-up&#8230;  The tiered compilation stuff that Steve Goldman of Sun was working on would of course help with that if you got a light C1 quickly and then C2 when needed:</p>
<p><a href="http://blogs.sun.com/fatcatair/category/Java" rel="nofollow">http://blogs.sun.com/fatcatair/category/Java</a></p>
<p>But also I&#8217;d suggested to him to simply remember which methods had been hot at startup but didn&#8217;t run long enough after being compiled to get much benefit from compilation.  On a subsequent run those would be compiled as soon as (and this before) they were called (C1 level I guess) like an old-fashioned JIT.</p>
<p>Much safer and less data and dependencies to store than a code cache, and the worst that can really happen is some excess compilation for things that turned out not to be early/start-up hotspots *this* time, eg because the code was changed.</p>
<p>Java could really benefit from having such work folded back in IMHO&#8230;</p>
<p>Rgds</p>
<p>Damon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damon Hart-Davis</title>
		<link>http://labb.zafena.se/?p=282#comment-4892</link>
		<dc:creator>Damon Hart-Davis</dc:creator>
		<pubDate>Sat, 10 Oct 2009 07:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://labb.zafena.se/?p=282#comment-4892</guid>
		<description>Ah, good work!  And luckily I don't think I care about most of the parts that Shark is handling less well unless network I/O gets snarled up the same way in JNI stuff!  B^&#62;

Rgds

Damon</description>
		<content:encoded><![CDATA[<p>Ah, good work!  And luckily I don&#8217;t think I care about most of the parts that Shark is handling less well unless network I/O gets snarled up the same way in JNI stuff!  B^&gt;</p>
<p>Rgds</p>
<p>Damon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gbenson.net :: Long overdue update</title>
		<link>http://labb.zafena.se/?p=282#comment-4887</link>
		<dc:creator>gbenson.net :: Long overdue update</dc:creator>
		<pubDate>Fri, 09 Oct 2009 16:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://labb.zafena.se/?p=282#comment-4887</guid>
		<description>[...] one last thing I want to do before I step aside for a couple of months. Xerxes Rånby posted some benchmarks of Zero, Shark, and the assembler interpreter on ARM; Shark is gratifyingly faster than everything [...]</description>
		<content:encoded><![CDATA[<p>[...] one last thing I want to do before I step aside for a couple of months. Xerxes Rånby posted some benchmarks of Zero, Shark, and the assembler interpreter on ARM; Shark is gratifyingly faster than everything [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
