caiwei-ebay edited a comment on pull request #158: URL: https://github.com/apache/maven-resolver/pull/158#issuecomment-1069797740
> Am getting consistently slower results (2nd, 3rd run), but unsure is it skipper or BFS that is on master? > > @caiwei-ebay could you tell more about those projects you refer to? I guess they are not open (if they are, please point us on them), but I wonder what they have in common: size (as in module count/reactor size)? are they using version ranges? Are they having unused dependencies (as you refer to "make dep tree clean, remove unused dependencies")...? @cstamas Thanks for the test report. The projects I mentioned in previous comment are company internal consuming internal artifacts from an internal maven repository based on Artifactory. The most common issue is heavy dependencies + different exclusions are widely used in project which make maven resolve duplicate node again and again. As to the heavy dependencies, they are formed after 10 years development with more and more dependencies added into their poms :). The maven build usually takes >5 minutes with tests skipped, this is why I say they are complex projects. I'm not sure if I can find a opensource project that can reproduce such issue, even entire spring-boot project can print dependency:tree in 20s and does not have such issue. let me try to find one. Regarding the test method, could you please build mvn bfs with code checked out before the "BFS approach" commit and run the performance test? This can help narrow down the root causes, either because of the BFS commit or commits before BFS. This means the 1st case would be: - mvn 3.8.5 (resolver 1.6.x + wagon) -> mvn bfs (use last commit before BFS PR, [here](https://github.com/bfs-skip/maven-resolver/commit/1c79c4f8b6573e9693f4ae61c14bff17755aa32d)) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
