[
http://jira.codehaus.org/browse/MNG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112030
]
Stefan Behnel commented on MNG-3222:
------------------------------------
We are using an in-house repository server via HTTP. It pings in less than 4ms,
so I don't think latency is an issue here. For the last version, we have about
200 snapshots lying around per module. That makes some 700-1000 files per
module. Serving a directory listing for them shouldn't be a problem for a web
server (especially since I would expect the whole directory tree to be cached
in RAM pretty soon), so I wouldn't expect the problem to be on the server side.
Our modules have up to 250 transitive dependencies, while I would expect the
average to be much lower. So let's say we have some 100 directory listings per
module. A listing page is between 70K and 130K and wget retrieves it in less
than 0.3 seconds. That would make it at most 30 seconds for the listings or
about one minute if we count 250 dependencies. Compile time resolution takes
about 3 minutes in total for 250 dependencies, that means we are already coming
somewhat close to the times we see here, *iff* we really access the server. It
doesn't explain the remaining difference of 2/3 of the time, though. BTW,
keeping the HTTP connection open during the build (possibly only for directory
listings) would likely drop the access time quite a bit, I don't know if Maven
does this.
However, snapshot resolution happens once per day by default. But even if I
re-run the build multiple times, I do not see that the times drop by a major
extent. So I'm still convinced that the problem is not external to Maven.
> Compile dependency resolution is slow
> -------------------------------------
>
> Key: MNG-3222
> URL: http://jira.codehaus.org/browse/MNG-3222
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Stefan Behnel
> Assignee: Brett Porter
>
> Compile dependency resolution is slow. I just wrote an empty module (only
> test sources that were not compiled), and it took Maven more than five
> minutes to build it, without any compilation/generation/testing/whatsoever. I
> just took literally minutes to resolve a couple of hundred compile time
> dependencies for the compiler plugin, which was then executed twice.
> To me, this sounds like a problem with the algorithmic complexity of the
> dependency resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
