The following comment has been added to this issue:
Author: Dominique Collette
Created: Thu, 15 Apr 2004 11:24 AM
Body:
Hi Brett,
I work with Vincent. I'm looking at maven-1.0-rc3-SNAPSHOT's sources and the
WerkzDependencyResolver that it uses calls addPrecursor() from buildGraph().
We're currently running on :
480RSystem = SunOS
Node = XXXXXX
Release = 5.9
KernelID = Generic_112233-07
Machine = sun4u
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 2
With at least 2Gigs of RAM, 1Gig HD partition.
JDK :
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06), and I've also
tried with an older version of 1.4.2.
I let maven's reactor run on all 58 projects overnight to see if it would ever resolve
the dependency graph, and after approximately 3 hours, it finally did.
Since then, we've distributed the 58 maven projects in 3 separate maven reactors. It's
running fine now.
That said, I am definitely not ruling out the possibility that the box has a config
problem, because everything works fine under W2K, 1Gig RAM, 40 Gig HD.
If you need more info on my sys configs, don't hesitate.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1235&page=comments#action_18649
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=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, 15 Apr 2004 11:24 AM
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
