最近用maven2.2.1编译应用,发现竟然要5min。而类似代码规模的另一个应用,编译只要1min。查了一下,原因还是很狗血。
[INFO] ------------------------------------------------------------------------
[INFO] app-1
[INFO] Total time: 5 minutes 48 seconds
[INFO] Finished at: Sat Jan 19 15:52:09 HKT 2013
[INFO] Final Memory: 453M/1536M
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] app-2
[INFO] Total time: 1 minute 52 seconds
[INFO] Finished at: Sat Jan 19 15:48:31 HKT 2013
[INFO] Final Memory: 370M/986M
[INFO] ------------------------------------------------------------------------
开始发现gc比较夸张,一秒full一次,所以调了ms,结果一样慢。
后来jstack看到很多异常栈。发现是 Integer.valueOf("RELEASE")搞出来的,修改maven打包,还是很慢。
2\ profile
没有办法,默默鄙视自己100次,然后装了jprofiler。
cpu profile一看,问题就基本定位了。
两个应用都调用了 retrieveRelocatedArtifact,但是慢的那个占比明显多。很可能是调用次数变多。
于是再默默鄙视自己100次,手工加count,然后shutdownhook里打印出来(不会用btrace的人伤不起啊。。。)。发现是buildFromRepository开始变多的。
debug了下代码,发现是因为使用RELEASE版本号(LATEST类似)之后,maven编译的一个缓存map失效了(名字对不起来),具体原因是:
maven内部使用了一个map缓存每次parse pom文件的结果。使用RELEASE之后,缓存的key不固定。查找key的格式是“com.foo:bar:RELEASE”,但设置key的格式变成“com.foo.bar:1.0.1”,也就是具体的版本号。所以对RELEASE版本的依赖会重复处理,工程越多(pom越多),重复越多,速度也就越慢。
看看代码也许更明白:
public class DefaultMavenProjectBuilder extends AbstractLogEnabled
implements MavenProjectBuilder, Initializable, Contextualizable
{
private Map processedProjectCache = new HashMap();
public MavenProject buildFromRepository( Artifact artifact,...) {
String cacheKey = createCacheKey( artifact.getGroupId(), artifact.getArtifactId(), artifact.getVersion() ); // <========= the "get key"
MavenProject project = (MavenProject) processedProjectCache.get( cacheKey );
if ( project != null )
{
return project;
}
Model model = findModelFromRepository( artifact, remoteArtifactRepositories, localRepository, allowStubModel );
ProjectBuilderConfiguration config = new DefaultProjectBuilderConfiguration().setLocalRepository( localRepository );
MavenProject mavenProject = buildInternal("Artifact [" + artifact + "]", model, config, remoteArtifactRepositories,
null, false);
return mavenProject;
}
private MavenProject buildInternal(String pomLocation,
Model model,
ProjectBuilderConfiguration config,
List parentSearchRepositories,
File projectDescriptor,
boolean strict, String cacheKey)
throws ProjectBuildingException
{
//...
cacheKey = createCacheKey( project.getGroupId(), project.getArtifactId(), project.getVersion() ); // <========= the "set key"
processedProjectCache.put( cacheKey, project );
//...
}
}
3\ 修改对应代码,重新编译
[INFO] ------------------------------------------------------------------------
[INFO] app-1
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 57 seconds
[INFO] Finished at: Sat Jan 19 17:11:40 HKT 2013
[INFO] Final Memory: 422M/1004M
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] app-2
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 58 seconds
[INFO] Finished at: Sat Jan 19 17:10:35 HKT 2013
[INFO] Final Memory: 350M/941M
[INFO] ------------------------------------------------------------------------
4\ 关于REELASE和LATEST的补充说明
maven论坛很多帖说LATEST和RELEASE已经不推荐使用。maven官网的mvnref-book里的对应章节也找不到关于LASTEST和RELEASE的描述了。
https://issues.sonatype.org/browse/MVNREF-23
http://maven.40175.n5.nabble.com/LATEST-RELEASE-dependency-version-td124018.html
所以,把上面的bug提到stackoverflow以后,一个maven的commiter说别用RELEASE了。
于是,我也不好说啥了。
5\ 如何编译maven
5.1\
从 http://maven.apache.org/download.cgi 下载source
5.2\
cd /home/brian/work.sc/maven_src/apache-maven-2.2.1;
export M2_HOME=/home/brian/Desktop/apache-maven-2.2.1; export PATH=$M2_HOME/bin:$PATH
ant;
5.3\
cd $path_to_your_app;
export M2_HOME=/home/brian/Desktop/apache-maven-2.2.1; export PATH="$M2_HOME/bin:$PATH
mvn clean install -Dmaven.test.skip -Dcheck.parent.skip=false
ps, edit `which mvn` to enable remote debug