You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by pa...@targetgroup.net on 2008/06/19 13:59:28 UTC
Resolve times for IVY 2 beta
One of the most noticeable things about switching from IVY 1 to IVY 2 is
that the resolve times go through the roof. Using an ivyConf.xml that has
been converted to an ivySettings file (i.e. the same configuration for IVY
1 and IVY 2), IVY 1 resolves take a a few seconds, IVY 2 resolves can take
up to an hour. We have installed a team repository to mitigate the
problems, but installing bundles into this is currently really, really slow
in IVY 2.
There was a thread from October entitled "Extremely Slow to Resolve" so it
seems others have had this problem too.
Anyone any ideas ?
Target
www.targetgroup.net
Target is a trading name of Target Group Limited,
registered in England and Wales No. 1208137
Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
**********************************************************************
DISCLAIMER.
This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient you must not copy,
distribute or take any action or reliance upon it.
The content of this message may also contain personal
views of an employee of this company and does
not necessarily represent the view of the company.
**********************************************************************
This message has been scanned by Norton Anti-Virus.
It has also been scanned by MAILsweeper to enforce our e-mail
policy. If you have any concerns or comments about the content
of this message, please e-mail support@targetgroup.net.
**********************************************************************
_____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
Re: Resolve times for IVY 2 beta
Posted by pa...@targetgroup.net.
Everything is fine in Ivy 1 but not in Ivy 2, the settings are identical
between the two. The cache issuee, well, it can take 15 minutes just doing
the resolve, and I presume there is no cache issue there.
I've had trouble building the trunk from home (some weird Java security
issue), but will try again tonight o a clean box, and see if the localhost
fix there solves the problem.
Target
www.targetgroup.net
Target is a trading name of Target Group Limited,
registered in England and Wales No. 1208137
Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
**********************************************************************
DISCLAIMER.
This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient you must not copy,
distribute or take any action or reliance upon it.
The content of this message may also contain personal
views of an employee of this company and does
not necessarily represent the view of the company.
**********************************************************************
This message has been scanned by Norton Anti-Virus.
It has also been scanned by MAILsweeper to enforce our e-mail
policy. If you have any concerns or comments about the content
of this message, please e-mail support@targetgroup.net.
**********************************************************************
_____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
Re: Resolve times for IVY 2 beta
Posted by Dan North <ta...@gmail.com>.
Have you tried relocating the cache?
At one point we noticed ivy was very slow to resolve for some of the guys in
the team. It turns out the default location for the ivy cache is relative to
the users' home directory, which was a network share. We changed the default
cache location in the project ivysettings.xml and it sped up resolution by
orders of magnitude. (The build was much faster too because all the cached
jars were now local.)
This would also tie in with the slow "download" times - it might not be
ibiblio but your home share that's running slow.
Cheers,
Dan
2008/6/20 Xavier Hanin <xa...@gmail.com>:
> On Fri, Jun 20, 2008 at 10:25 AM, <pa...@targetgroup.net> wrote:
>
> >
> >
> >
> >
> > I've added the logging and the results are below. How do I get the latest
> > version from the trunk ? Our firewall blocks subversion access so I
> cannot
> > check it out and build it.
>
> Did you try with https instead of http access? Usually firewalls don't
> block
> svn through https traffic.
>
>
> >
> >
> > Here's the log, a cool 8 minutes 39 seconds to install commons-lang :-)
> >
> > resolved "commons-lang#commons-lang;2.0" (968ms)
> > resolved "commons-lang#commons-lang;2.0" (0ms)
> > resolved "commons-lang#commons-lang;2.0" (0ms)
> > resolved "commons-lang#commons-lang;2.0" (0ms)
> > resolved "commons-lang#commons-lang;2.0" (2860ms)
> >
> > The console output:
> >
> >
> > Buildfile: C:\Documents and
> > Settings\pauln\workspacejazz\CommonBaseCore\iv2.xml
> > init-basic:
> > [ivy:settings] :: Ivy 2.0.0-beta2 - 20080225093827 ::
> > http://ant.apache.org/ivy/ ::
> > [ivy:settings] :: loading settings :: file = C:\Documents and
> > Settings\pauln\workspacejazz\CommonBaseCore\ivySettings.xml
> > basic:
> > [ivy:install] :: installing commons-lang#commons-lang;2.0 ::
> > [ivy:install] :: resolving dependencies ::
> > [ivy:install] found commons-lang#commons-lang;2.0 in maven2
> > [ivy:install] :: downloading artifacts to cache ::
> > [ivy:install] downloading
> >
> >
> http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-lang/commons-lang/2.0/commons-lang-2.0.jar
> > ...
> > [ivy:install] .......
> > [ivy:install] . (165kB)
> > [ivy:install] .. (0kB)
> > [ivy:install] [SUCCESSFUL ]
> > commons-lang#commons-lang;2.0!commons-lang.jar (2860ms)
> > [ivy:install] :: installing in team ::
> > [ivy:install] published commons-lang to
> >
> >
> \\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.jar
> > [ivy:install] published ivy to
> >
> >
> \\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.xml
> > [ivy:install] publish commited: moved
> >
> >
> \\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0.part
> >
> > [ivy:install] to
> > \\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0
> > [ivy:install] :: install resolution report ::
> > [ivy:install] :: resolution report :: resolve 0ms :: artifacts dl 2875ms
>
> According to this log, it's really the download which takes so long.
> IBiblio
> is sometimes very slow, are you sure the problem doesn't come from here? I
> mean, try to use the same settings with Ivy 1.4 and Ivy 2, both with a
> clean
> cache, and see what happens. To consider the performance problem as related
> to Ivy you should better use a repository set up in your own network, where
> you can be confident with the repsonse time.
>
>
> Xavier
>
Re: Resolve times for IVY 2 beta
Posted by Xavier Hanin <xa...@gmail.com>.
On Fri, Jun 20, 2008 at 10:25 AM, <pa...@targetgroup.net> wrote:
>
>
>
>
> I've added the logging and the results are below. How do I get the latest
> version from the trunk ? Our firewall blocks subversion access so I cannot
> check it out and build it.
Did you try with https instead of http access? Usually firewalls don't block
svn through https traffic.
>
>
> Here's the log, a cool 8 minutes 39 seconds to install commons-lang :-)
>
> resolved "commons-lang#commons-lang;2.0" (968ms)
> resolved "commons-lang#commons-lang;2.0" (0ms)
> resolved "commons-lang#commons-lang;2.0" (0ms)
> resolved "commons-lang#commons-lang;2.0" (0ms)
> resolved "commons-lang#commons-lang;2.0" (2860ms)
>
> The console output:
>
>
> Buildfile: C:\Documents and
> Settings\pauln\workspacejazz\CommonBaseCore\iv2.xml
> init-basic:
> [ivy:settings] :: Ivy 2.0.0-beta2 - 20080225093827 ::
> http://ant.apache.org/ivy/ ::
> [ivy:settings] :: loading settings :: file = C:\Documents and
> Settings\pauln\workspacejazz\CommonBaseCore\ivySettings.xml
> basic:
> [ivy:install] :: installing commons-lang#commons-lang;2.0 ::
> [ivy:install] :: resolving dependencies ::
> [ivy:install] found commons-lang#commons-lang;2.0 in maven2
> [ivy:install] :: downloading artifacts to cache ::
> [ivy:install] downloading
>
> http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-lang/commons-lang/2.0/commons-lang-2.0.jar
> ...
> [ivy:install] .......
> [ivy:install] . (165kB)
> [ivy:install] .. (0kB)
> [ivy:install] [SUCCESSFUL ]
> commons-lang#commons-lang;2.0!commons-lang.jar (2860ms)
> [ivy:install] :: installing in team ::
> [ivy:install] published commons-lang to
>
> \\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.jar
> [ivy:install] published ivy to
>
> \\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.xml
> [ivy:install] publish commited: moved
>
> \\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0.part
>
> [ivy:install] to
> \\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0
> [ivy:install] :: install resolution report ::
> [ivy:install] :: resolution report :: resolve 0ms :: artifacts dl 2875ms
According to this log, it's really the download which takes so long. IBiblio
is sometimes very slow, are you sure the problem doesn't come from here? I
mean, try to use the same settings with Ivy 1.4 and Ivy 2, both with a clean
cache, and see what happens. To consider the performance problem as related
to Ivy you should better use a repository set up in your own network, where
you can be confident with the repsonse time.
Xavier
Re: Resolve times for IVY 2 beta
Posted by pa...@targetgroup.net.
I've added the logging and the results are below. How do I get the latest
version from the trunk ? Our firewall blocks subversion access so I cannot
check it out and build it.
Here's the log, a cool 8 minutes 39 seconds to install commons-lang :-)
resolved "commons-lang#commons-lang;2.0" (968ms)
resolved "commons-lang#commons-lang;2.0" (0ms)
resolved "commons-lang#commons-lang;2.0" (0ms)
resolved "commons-lang#commons-lang;2.0" (0ms)
resolved "commons-lang#commons-lang;2.0" (2860ms)
The console output:
Buildfile: C:\Documents and
Settings\pauln\workspacejazz\CommonBaseCore\iv2.xml
init-basic:
[ivy:settings] :: Ivy 2.0.0-beta2 - 20080225093827 ::
http://ant.apache.org/ivy/ ::
[ivy:settings] :: loading settings :: file = C:\Documents and
Settings\pauln\workspacejazz\CommonBaseCore\ivySettings.xml
basic:
[ivy:install] :: installing commons-lang#commons-lang;2.0 ::
[ivy:install] :: resolving dependencies ::
[ivy:install] found commons-lang#commons-lang;2.0 in maven2
[ivy:install] :: downloading artifacts to cache ::
[ivy:install] downloading
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-lang/commons-lang/2.0/commons-lang-2.0.jar
...
[ivy:install] .......
[ivy:install] . (165kB)
[ivy:install] .. (0kB)
[ivy:install] [SUCCESSFUL ]
commons-lang#commons-lang;2.0!commons-lang.jar (2860ms)
[ivy:install] :: installing in team ::
[ivy:install] published commons-lang to
\\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.jar
[ivy:install] published ivy to
\\tgcrepd1\ivy-repository/repositorymaven/commons-lang/commons-lang/2.0.part/commons-lang-2.0.xml
[ivy:install] publish commited: moved
\\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0.part
[ivy:install] to
\\tgcrepd1\ivy-repository\repositorymaven\commons-lang\commons-lang\2.0
[ivy:install] :: install resolution report ::
[ivy:install] :: resolution report :: resolve 0ms :: artifacts dl 2875ms
---------------------------------------------------------------------
| | modules || artifacts |
| conf | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
| default | 1 | 1 | 1 | 0 || 1 | 1 |
---------------------------------------------------------------------
BUILD SUCCESSFUL
Total time: 8 minutes 39 seconds
and the settings:
<ivysettings>
<!--
see http://www.jayasoft.org/ivy/doc/configuration
-->
<!-- you can override this property to use mirrors
http://mirrors.dotsrc.org/maven2
http://ftp.ggi-project.org/pub/packages/maven2
http://mirrors.sunsite.dk/maven2
http://public.planetmirror.com/pub/maven2
http://ibiblio.lsu.edu/main/pub/packages/maven2
http://www.ibiblio.net/pub/packages/maven2
-->
<property name="ibiblio-maven2-root"
value="http://www.ibiblio.org/maven2/" override="false"/>
<property name="jboss"
value="http://repository.jboss.com/maven2/" override="false"/>
<property name="mvnrepository"
value="http://mvnrepository.com/" override="false"/>
<property name="javarepo"
value="http://javarepo.xoocode.org//" override="false"/>
<property name="ibiblio"
value="http://mirrors.ibiblio.org/pub/mirrors/maven2/"
override="false"/>
<property name="spring-root"
value="http://www.springsource.com/repository/app/"
override="false"/>
<property name="maven2.pattern"
value="[organisation]/[module]/[revision]/[module]-[revision]" />
<property name="maven2.pattern.ext"
value="${maven2.pattern}.[ext]" />
<property name="ivy2.pattern"
value="[organisation][module]/[revision]/[artifact]-[revision]" />
<property name="ivy2.pattern.ext"
value="${ivy2.pattern}.[ext]" />
<property name="ivy-repository"
value="\\tgcrepd1\ivy-repository" />
<!-- pull in the local repository -->
<include url="${ivy.default.conf.dir}/ivyconf-local.xml"/>
<settings defaultResolver="default"/>
<resolvers>
<filesystem name="team">
ivys="true" artifacts="true"
m2compatible="true" >
<artifact
pattern="${ivy-repository}/repositorymaven/${maven2.pattern.ext}"/>
<ivy
pattern="${ivy-repository}/repositorymaven/${maven2.pattern}.xml"/>
</filesystem>
<filesystem name="teamivy">
ivys="true" artifacts="true"
m2compatible="false" >
<artifact
pattern="${ivy-repository}/repositoryivy/${ivy2.pattern.ext}"/>
<ivy pattern="${ivy-repository}/repositoryivy/${ivy2.pattern}.xml"/>
</filesystem>
<url name="com.springsource.repository.bundles.release">
<ivy
pattern="http://repository.springsource.com/ivy/bundles/release/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="http://repository.springsource.com/ivy/bundles/release/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
<url name="com.springsource.repository.bundles.external">
<ivy
pattern="http://repository.springsource.com/ivy/bundles/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="http://repository.springsource.com/ivy/bundles/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
<url name="com.springsource.repository.libraries.release">
<ivy
pattern="http://repository.springsource.com/ivy/libraries/release/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="http://repository.springsource.com/ivy/libraries/release/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
<url name="com.springsource.repository.libraries.external">
<ivy
pattern="http://repository.springsource.com/ivy/libraries/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
<artifact
pattern="http://repository.springsource.com/ivy/libraries/external/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
<ibiblio name="javarepo"
root="${javarepo}"
pattern="${maven2.pattern.ext}"
m2compatible="true"
/>
<ibiblio name="maven2"
root="${ibiblio}"
pattern="${maven2.pattern.ext}"
m2compatible="true"
/>
<chain name="default" dual="true">
<resolver ref="teamivy"/>
<resolver ref="com.springsource.repository.bundles.release"/>
<resolver ref="com.springsource.repository.bundles.external"/>
<resolver ref="maven2"/>
</chain>
<chain name="internal">
<resolver ref="local"/>
<resolver ref="teamivy"/>
</chain>
</resolvers>
<modules>
<module organisation="net.targetgroup" name=".*" resolver="internal"/>
</modules>
<triggers>
<log file="ivy.log"
message='resolved "${organisation}#${module};${revision}"
(${duration}ms)'
event="post-download-artifact" />
</triggers>
</ivysettings>
Target
www.targetgroup.net
Target is a trading name of Target Group Limited,
registered in England and Wales No. 1208137
Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
**********************************************************************
DISCLAIMER.
This message is intended only for the use of the Addressee and may
contain information that is PRIVILEGED and CONFIDENTIAL.
If you are not the intended recipient you must not copy,
distribute or take any action or reliance upon it.
The content of this message may also contain personal
views of an employee of this company and does
not necessarily represent the view of the company.
**********************************************************************
This message has been scanned by Norton Anti-Virus.
It has also been scanned by MAILsweeper to enforce our e-mail
policy. If you have any concerns or comments about the content
of this message, please e-mail support@targetgroup.net.
**********************************************************************
_____________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
Re: Resolve times for IVY 2 beta
Posted by Xavier Hanin <xa...@gmail.com>.
On Thu, Jun 19, 2008 at 1:59 PM, <pa...@targetgroup.net> wrote:
>
>
>
>
> One of the most noticeable things about switching from IVY 1 to IVY 2 is
> that the resolve times go through the roof. Using an ivyConf.xml that has
> been converted to an ivySettings file (i.e. the same configuration for IVY
> 1 and IVY 2), IVY 1 resolves take a a few seconds, IVY 2 resolves can take
> up to an hour. We have installed a team repository to mitigate the
> problems, but installing bundles into this is currently really, really slow
> in IVY 2.
>
> There was a thread from October entitled "Extremely Slow to Resolve" so it
> seems others have had this problem too.
>
> Anyone any ideas ?
If the only difference is Ivy 1 vs Ivy 2, it's really a problem, I see no
reason why things can be so slow. One good thing with Ivy 2 is that you can
monitor its performance using triggers. For instance, try adding this to
your settings:
<triggers>
<log file="ivy.log"
message='resolved "${organisation}#${module};${revision}"
(${duration}ms)'
event="post-download-artifact" />
</triggers>
Then run a build and check the ivy.log file. It might help understanding
what goes wrong. Another hint is to use the debug mode, and see if Ivy halts
at some particular cases. There's also one thing which may cause the problem
which Maarten fixed recently: improper usage of localhost name lookup. So
try out the trunk version to see if it works better, and keep us informed.
Xavier
>
>
>
>
> Target
> www.targetgroup.net
>
> Target is a trading name of Target Group Limited,
> registered in England and Wales No. 1208137
> Registered office: Target House, Cowbridge Road East, Cardiff CF11 9AU
>
> **********************************************************************
> DISCLAIMER.
> This message is intended only for the use of the Addressee and may
> contain information that is PRIVILEGED and CONFIDENTIAL.
> If you are not the intended recipient you must not copy,
> distribute or take any action or reliance upon it.
> The content of this message may also contain personal
> views of an employee of this company and does
> not necessarily represent the view of the company.
> **********************************************************************
> This message has been scanned by Norton Anti-Virus.
> It has also been scanned by MAILsweeper to enforce our e-mail
> policy. If you have any concerns or comments about the content
> of this message, please e-mail support@targetgroup.net.
> **********************************************************************
>
>
> _____________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs Email
> Security System. For more information on a proactive email security
> service working around the clock, around the globe, visit
> http://www.messagelabs.com
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/