<?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>Comentarios en: Lua JIT (Just in Time Compiler)</title>
	<atom:link href="http://www.pplux.com/2005/12/06/lua-jit-just-in-time-compiler/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pplux.com/2005/12/06/lua-jit-just-in-time-compiler/</link>
	<description>el blog de PpluX</description>
	<pubDate>Mon, 01 Dec 2008 21:04:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Mike</title>
		<link>http://www.pplux.com/2005/12/06/lua-jit-just-in-time-compiler/#comment-64</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 06 Dec 2005 22:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pplux.com/?p=55#comment-64</guid>
		<description>Yes, the Lua interpreter is already very fast. But this is only part of the reason why the LuaJIT speedups are 'conservative'.

The published speedups come from 'real' benchmarks and not from some micro benchmarks (usually one-liners). I can easily come up with several micro 'benchmarks' that show a 30x speedup with LuaJIT. But I regard this as dishonest.

Telling people they won't see a speedup if they mainly use C library calls (i.e. the 1.04x figure) is maybe bad marketing, but also something they need to consider.

For a real cross-language comparison look at http://shootout.alioth.debian.org/ and at http://shootout.alioth.debian.org/gp4/ . Please note that Lua gets its speed without using tons of calls to C functions (like Python does) and still beats Python and Perl easily. Then compare Lua to Psyco (only in the gp4 set) and you'll be enlightened.

LuaJIT is not in there (yet), but would score significantly higher on the pure CPU benchmark score (change the weights to 1, 0, 0 in the form). Somewhere around the Java scores (JIT compiled Java, not the Java interpreter).

E.g. LuaJIT 1.0.3 gets around 50% of the speed of fully-optimized and hand-tuned C code in the mandelbrot benchmark. That's not so bad for a JIT engine that fits in only 25 Kilobytes IMHO.</description>
		<content:encoded><![CDATA[<p>Yes, the Lua interpreter is already very fast. But this is only part of the reason why the LuaJIT speedups are &#8216;conservative&#8217;.</p>
<p>The published speedups come from &#8216;real&#8217; benchmarks and not from some micro benchmarks (usually one-liners). I can easily come up with several micro &#8216;benchmarks&#8217; that show a 30x speedup with LuaJIT. But I regard this as dishonest.</p>
<p>Telling people they won&#8217;t see a speedup if they mainly use C library calls (i.e. the 1.04x figure) is maybe bad marketing, but also something they need to consider.</p>
<p>For a real cross-language comparison look at <a href="http://shootout.alioth.debian.org/" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/shootout.alioth.debian.org');">http://shootout.alioth.debian.org/</a> and at <a href="http://shootout.alioth.debian.org/gp4/" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/shootout.alioth.debian.org');">http://shootout.alioth.debian.org/gp4/</a> . Please note that Lua gets its speed without using tons of calls to C functions (like Python does) and still beats Python and Perl easily. Then compare Lua to Psyco (only in the gp4 set) and you&#8217;ll be enlightened.</p>
<p>LuaJIT is not in there (yet), but would score significantly higher on the pure CPU benchmark score (change the weights to 1, 0, 0 in the form). Somewhere around the Java scores (JIT compiled Java, not the Java interpreter).</p>
<p>E.g. LuaJIT 1.0.3 gets around 50% of the speed of fully-optimized and hand-tuned C code in the mandelbrot benchmark. That&#8217;s not so bad for a JIT engine that fits in only 25 Kilobytes IMHO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
