You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/10/14 18:25:21 UTC
[jira] Updated: (MAVEN-1235) Performance problem with Maven reactor on Solaris
The following issue has been updated:
Updater: Eric Lapierre (mailto:ericlap@nortelnetworks.com)
Date: Thu, 14 Oct 2004 12:25 PM
Comment:
This is an example that replicates our project structure, the dependencies between the projects, as well as 3rd party jar dependencies. This takes forever on Solaris 9.
Changes:
Attachment changed to with_3rd_party_dependencies.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1235?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1235
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1235
Summary: Performance problem with Maven reactor on Solaris
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0-beta-10
1.0-rc3
1.0-rc1
1.0-rc2
Assignee:
Reporter: Vincent Massol
Created: Wed, 14 Apr 2004 5:01 AM
Updated: Thu, 14 Oct 2004 12:25 PM
Description:
Context:
We have about 58 Maven projects. Each project has about 85 dependencies. About 50 of these are dependencies to external jars. The rest are inter-project dependencies.
Problem:
When running the Maven reactor on windows machine. The reactor correctly and relatively quickly (30-40 seconds) finds out the ordered list of projects to run. However, on Solaris, it takes about 215 minutes (almost 4 hours!) to find out the ordered list of projects.
Analysis:
It seems the problem is somewhere in the werkz code. When using a profiling tool, 100% of the time is spent in the Goal.addPrecusor method (which takes as an average about 1 minute per project per dependency to run). I don't see how the problem could be in werkz. But still the profiling tool points there.
Could it be the checkForCycle which is somehow having recursivity problems on Solaris?
Any idea?
Thanks
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org