Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Sat, 21 Mar 2015 17:39:38 +0000 (UTC)
From: "Eduardo Jimenez (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <JIRA.12366881.1176196398000.167677.1426959578128@Atlassian.JIRA>
In-Reply-To: <JIRA.12366881.1176196398000@Atlassian.JIRA>
References: <JIRA.12366881.1176196398000@Atlassian.JIRA>
 <JIRA.12366881.1176196398699@arcas>
Subject: [jira] [Commented] (IVY-469) Parallelize artifact downloading
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/IVY-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372915#comment-14372915 ] 

Eduardo Jimenez commented on IVY-469:
-------------------------------------

I'm a bit surprised there aren't more votes here, since in my experience countless hours are spent (for various valid or invalid reasons) waiting for artifact download in a variety of cases.

Release builds are usually executed without caching. In large modern projects with hundreds of dependences, one ends up waiting 10 minutes while dependencies are resolved and downloaded, even in reasonably fast networks.

For most projects its of course arguably overkill. And most developers rebuild their ivy cache maybe only a few times a year so overall not a huge problem from that perspective.

For release builds though, it would make them go significantly faster, IMHO. And in these days of SSDs and fast networks, it would be a nice option for those times where you do have a large number of uncached dependencies.

> Parallelize artifact downloading
> --------------------------------
>
>                 Key: IVY-469
>                 URL: https://issues.apache.org/jira/browse/IVY-469
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Xavier Hanin
>
> For the moment artifact downloading during dependencies resolution happens sequentially, each artifact being downloaded one after the other.
> It would be nice to improve Ivy resolve engine to be able to parallelize downloading to optimize performance, especially when using a set of repositories with heterogeneous performance.
> We should see how load balancing feature of IVY-468 could be leveraged by this new downloading strategy.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)