[
https://issues.apache.org/jira/browse/MAPREDUCE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792667#action_12792667
]
Todd Lipcon commented on MAPREDUCE-1114:
----------------------------------------
The issue is that the build ends up spawning a lot of subants, which each
re-resolve everything. I get a total of 22 ivy-resolves even if I skip contrib!
Part of this is that skip.contrib=1 still resolves all of the contrib stuff
(MAPREDUCE-1113)
{quote}
t...@todd-laptop:~/git/hadoop-mapreduce$ ant test -Dskip.contrib=1
-Dtestcase=xxx 2>&1 | grep 'ivy-resolve' | wc -l
22
t...@todd-laptop:~/git/hadoop-mapreduce$ ant test -Dskip.contrib=1
-Dtestcase=xxx 2>&1 | grep 'ivy-resolve-common' | wc -l
19
{quote}
Some of these are within the same ant run, so they get cached. But 16 of them
actually do some non-cached work:
{quote}
t...@todd-laptop:~/git/hadoop-mapreduce$ ant test -Dskip.contrib=1
-Dtestcase=xxx 2>&1 | grep 'resolving dependencies' | wc -l
16
{quote}
> Speed up ivy resolution in builds with clever caching
> -----------------------------------------------------
>
> Key: MAPREDUCE-1114
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1114
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: mapreduce-1114.txt, mapreduce-1114.txt,
> mapreduce-1114.txt
>
>
> An awful lot of time is spent in the ivy:resolve parts of the build, even
> when all of the dependencies have been fetched and cached. Profiling showed
> this was in XML parsing. I have a sort-of-ugly hack which speeds up
> incremental compiles (and more importantly "ant test") significantly using
> some ant macros to cache the resolved classpaths.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
