maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] (MDEP-421) Unpack Incredibly Slow for
Date Wed, 11 Sep 2013 06:24:52 GMT


Kristian Rosenvold commented on MDEP-421:

There is an abundance of platform-specific/jdk version specific solutions in this area. Just
to illustrate:

    $ time mvn -q -B org.apache.maven.plugins:maven-dependency-plugin:2.6:unpack
    real    0m2.110s
    user    0m0.091s
    sys     0m0.076s
    $ time mvn -q -B org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
    real    0m2.111s
    user    0m0.060s
    sys     0m0.090s

This kind of performance regression is usually due to file attribute handling, which was handled
by forks for java versions prior to jdk7.

We need exact platform and java versions for this issue. You may also want to give 2.9-SNAPSHOT
a quick spin since it uses the latest version
of "everything". 
> Unpack Incredibly Slow for 
> ---------------------------
>                 Key: MDEP-421
>                 URL:
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: unpack-dependencies
>    Affects Versions: 2.8
>            Reporter: Mike Gilbode
> I've got a zipfile that is 240MB and has ~84k entries.  I'm trying to use unpack-dependencies
and it is taking an inordinate amount of time such that it is basically unusable.  It seems
that it's eagerly trying to read through every zip file entry before actually unpacking. 
This takes roughly 15 minutes where using the maven antrun plugin / unzip task takes less
than a minute.
>    java.lang.Thread.State: RUNNABLE
>         at java.util.Hashtable.put(
>         - locked <0x00000007e160ea18> (a java.util.Hashtable)
>         at
>         at<init>(
>         at
>         at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(
>         at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(
>         at org.apache.maven.plugin.dependency.fromDependencies.UnpackDependenciesMojo.doExecute(
>         at org.apache.maven.plugin.dependency.AbstractDependencyMojo.execute(
>         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
>         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
>         at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(
>         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
>         at org.apache.maven.DefaultMaven.doExecute(
>         at org.apache.maven.DefaultMaven.execute(
>         at org.apache.maven.cli.MavenCli.execute(
>         at org.apache.maven.cli.MavenCli.doMain(
>         at org.apache.maven.cli.MavenCli.main(
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke(
>         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
>         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
>         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
>         at org.codehaus.plexus.classworlds.launcher.Launcher.main(

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message