Groovyc takes a long time to work out that nothing needs compiling

[Peter Ledbrook-2]

Hi,

I'm currently looking into continuous testing for Grails, which would
basically mean that as soon as you save a class, any tests that are
affected will be run immediately. Of course, the first thing we need
to do is recompile the class. Unfortunately, ththe "groovyc" and task
is currently taking > 3s on my system to compile no files at all. This
makes the continuous testing idea fall slightly flat on its face.

So, are we probably using the "groovyc" task incorrectly, or is there
a problem in the current implementation that needs fixing?

Thanks,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

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

    http://xircles.codehaus.org/manage_email

[Peter Ledbrook-2]

> So, are we probably using the "groovyc" task incorrectly, or is there
> a problem in the current implementation that needs fixing?

Sorry, should have said that this is with Groovy 1.5.6.

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

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

    http://xircles.codehaus.org/manage_email

[XMaNIaC]

In my experience the compiler is just slow..

On Wed, Jul 2, 2008 at 5:17 PM, Peter Ledbrook <peter@...> wrote:

> So, are we probably using the "groovyc" task incorrectly, or is there
> a problem in the current implementation that needs fixing?

Sorry, should have said that this is with Groovy 1.5.6.

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

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

   http://xircles.codehaus.org/manage_email

[Peter Ledbrook-2]

2008/7/2 Jose Noheda <jose.noheda@...>:
> In my experience the compiler is just slow..

Well, in this case it seems that the Grails compiler class is adding a
hefty overhead. Still investigating the remaining 1 or 2 seconds.

Cheers,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

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

    http://xircles.codehaus.org/manage_email

[David Clark-9]

It is slower than javac, but within the last 4-5 months they have really
improved the compiler from where it was.  I can't remember which version it
was which had the major improvements, but my build times decreased by 4-5x
with that version.  While faster is always better, they are making
improvements.

On Wednesday 02 July 2008, Peter Ledbrook wrote:
> 2008/7/2 Jose Noheda <jose.noheda@...>:
> > In my experience the compiler is just slow..
--
David

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

    http://xircles.codehaus.org/manage_email

[Peter Ledbrook-2]

> Well, in this case it seems that the Grails compiler class is adding a
> hefty overhead. Still investigating the remaining 1 or 2 seconds.

Just to be clear: in the particular situation I'm describing, the
compiler is not even being invoked. The ant task *may* be adding some
overhead, but I don't know. We'll be looking into the Grails side of
things for now.

Thanks,

Peter

--
Software Engineer
G2One, Inc.
http://www.g2one.com/

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

    http://xircles.codehaus.org/manage_email

[Jochen Theodorou]

Jose Noheda schrieb:
> In my experience the compiler is just slow..

instead of saying "just slow" we should say "what is it, that is slow"?

when you look at the title "Groovyc takes a long time to work out that
nothing needs compiling"

Then you will see that the compiler itself is not even running. Because
the compiler compiles, without thinking if something is new or not. The
Groovyc task has a bit of logic that tests each file if it needs
compilation and that part is nearly equal to what the javac task has. So
there will be many file operations and it depends on the speed of your
idsc, how fast this phase can be accomplished. The only way to reduce
that would be to avoid the checks completely... no idea how this should
be done.

bye blackdrag

--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/
http://www.g2one.com/

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

    http://xircles.codehaus.org/manage_email