groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rahul Somasunderam <>
Subject Re: Suggestions for performance improvement
Date Sat, 18 Jul 2015 23:21:51 GMT
Thanks! I've created a JIRA to address the performance -

Rahul Somasunderam
Engineer, Transcend Insights

On Jul 18, 2015, at 10:31 AM, Keegan Witt <<>>

a) Not exactly.  In an earlier version of the code Rahul was experimenting with to compare
performance, he said "I couldn't get gradle to do that, possibly because there's java code
depending on groovy code and groovy code depending on java code."  I was curious about how
that could be solved, since GMavenPlus doesn't experience that issue.  Maybe I should have
started a new thread.

b) It's not perfect, but the solution was to let Groovy compile both the Groovy and the Java,
which Peter does in his first sourceSets example.  But if anybody has a better idea, I'd love
to hear about it.  Here's a simple project demonstrating the issue:


On Sat, Jul 18, 2015 at 12:52 PM, Jochen Theodorou <<>>
a) wrong thread? Or should I say: I miss why your post is a reply to my post
b) what exactly is there a solution to the circular compilation issue?

bye blackdrag

Am 18.07.2015 18:38, schrieb Keegan Witt:
FYI, Peter Niederwieser offered
<> a solution to the circular
compilation issue about a year ago.


On Tue, Jul 14, 2015 at 1:11 AM, Jochen Theodorou <<>
<<>>> wrote:

    Am 13.07.2015 22:20, schrieb Rahul Somasunderam:

        I'm assuming metaclass init should be a one time penalty. Or is
        something I'm misunderstanding about it?

    the big hit is a one time penalty, yes. meta classes might be
    created later on again because a meta class might have been garbage
    collected on too low memory. But first of all, you have a big hit in
    performance caused by reading in the extension methods and created
    the basic meta class infrastructure

    bye blackdrag

    Jochen "blackdrag" Theodorou

Jochen "blackdrag" Theodorou

The information transmitted is intended only for the person or entity to which it is addressed
and may contain CONFIDENTIAL material.  If you receive this material/information in error,
please contact the sender and delete or destroy the material/information.
View raw message