31 messages in org.codehaus.groovy.devRe: [groovy-dev] as usual on performa...
FromSent OnAttachments
Alex Tkachman27 Feb 2008 05:38 
Guillaume Laforge27 Feb 2008 05:47 
Alex Tkachman27 Feb 2008 06:01 
Chanwit Kaewkasi27 Feb 2008 06:21 
Martin C. Martin27 Feb 2008 06:27 
Jochen Theodorou27 Feb 2008 06:32 
Jochen Theodorou27 Feb 2008 06:33 
tugwilson27 Feb 2008 06:55 
Chanwit Kaewkasi27 Feb 2008 07:15 
Chanwit Kaewkasi27 Feb 2008 08:01 
Jochen Theodorou27 Feb 2008 08:28 
tugwilson27 Feb 2008 09:00 
tugwilson27 Feb 2008 09:55 
Chanwit Kaewkasi27 Feb 2008 11:27 
Chanwit Kaewkasi27 Feb 2008 11:31 
Jochen Theodorou27 Feb 2008 11:36 
Alex Tkachman27 Feb 2008 11:58 
Martin C. Martin27 Feb 2008 12:18 
Jochen Theodorou27 Feb 2008 12:37 
Jochen Theodorou27 Feb 2008 12:45 
tugwilson27 Feb 2008 12:48 
tugwilson27 Feb 2008 12:51 
Martin C. Martin27 Feb 2008 13:27 
Alex Tkachman27 Feb 2008 13:48 
tugwilson27 Feb 2008 14:14 
Jochen Theodorou27 Feb 2008 17:09 
Alexandru Popescu ☀27 Feb 2008 17:38 
Charles Oliver Nutter28 Feb 2008 00:20 
Jochen Theodorou28 Feb 2008 01:33 
Alexandru Popescu ☀28 Feb 2008 02:56 
tugwilson28 Feb 2008 03:29 
Subject:Re: [groovy-dev] as usual on performance - operations on primitives
From:Chanwit Kaewkasi (chan@gmail.com)
Date:02/27/2008 06:21:25 AM
List:org.codehaus.groovy.dev

Hi Alex,

P.S. Unfortunately 30-40% is much less than I expected :(

I've been reading some papers about trace-based Just-in-Time compilation, and what I've found out for Groovy is that there is not enough *type information* to feedback for JIT to optimize. This probably because Groovy class is not designed to be interpreted since the beginning.

What do you think?

Cheers,

Chanwit

-- Chanwit Kaewkasi PhD Student, Centre for Novel Computing School of Computer Science The University of Manchester Oxford Road Manchester M13 9PL, UK

--------------------------------------------------------------------- To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email