[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276628#comment-276628
]
Eran Harel commented on MJAR-140:
-
When will the 2.3.2 / 2.4 artifacts be available in the maven repository?
Performance degredation
Key: MJAR-140
URL: https://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x JAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.3.1
Reporter: Eran Harel
Assignee: Kristian Rosenvold
Fix For: 2.3.2
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276639#comment-276639
]
Kristian Rosenvold commented on MJAR-140:
-
2.3.2 is available now
Performance degredation
Key: MJAR-140
URL: https://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x JAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.3.1
Reporter: Eran Harel
Assignee: Kristian Rosenvold
Fix For: 2.3.2
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272148#comment-272148
]
Erez Mazor commented on MJAR-140:
-
Any updates on this issue?
Performance degredation
Key: MJAR-140
URL: https://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x JAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
https://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272150#comment-272150
]
Kristian Rosenvold commented on MJAR-140:
-
Yes, but it's not a simple answer.
The update to PlexusIoResourceCollection was done to achieve file attribute
correctness. So the incorrect behaviour was fast but the correct behaviour is
slower.
But all is not entirely lost. I have published pleus-archiver 2.0, plexus-io
2.0 and plexus-utils 3.0. If you add all of these to your plugin dependencies
you will get an improvement in performance. To get back to the original speed
you will actually have to use java 1.7. plexus-io 2.0 supports native file
attributes through the java 1.7 api's. So with java 1.7 you should see little
or no difference in performance from 2.2. For java 1.5/1.6, plexus-io 2.0 now
forks the two ls forks in parallel, which should help some on the observed
slowdown.
The slowdown affects all posix compliant systems.
Performance degredation
Key: MJAR-140
URL: https://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x JAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=269849#action_269849
]
Kristian Rosenvold commented on MJAR-140:
-
It would seem to me like this degradation occured when plexus-archiver switched
to using PlexusIoProxyResourceCollection which possibly retrieves quite a lot
of information we dont use. Especially on Linux this can be bad since plexus-io
still uses forks to determine file attributes, which I am still not sure if we
use/need.
Performance degredation
Key: MJAR-140
URL: http://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x JAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=249963#action_249963
]
Eran Harel commented on MJAR-140:
-
BTW, the 2.3.1 jar-plugin version has the same effect on maven 2.2.1 if it
helps.
Performance degredation
Key: MJAR-140
URL: http://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=249966#action_249966
]
Dennis Lundberg commented on MJAR-140:
--
Can you please try with version 2.3 of the plugin to see what results you get?
Performance degredation
Key: MJAR-140
URL: http://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAR-140) Performance degredation
[
http://jira.codehaus.org/browse/MJAR-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=249970#action_249970
]
Eran Harel commented on MJAR-140:
-
2.2 results:
{code}
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2:25.773s
[INFO] Finished at: Thu Dec 30 12:24:16 IST 2010
[INFO] Final Memory: 1001M/1575M
{code}
2.3 results
{code}
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 4:30.299s
[INFO] Finished at: Thu Dec 30 15:06:08 IST 2010
[INFO] Final Memory: 1014M/1831M
[INFO]
{code}
Performance degredation
Key: MJAR-140
URL: http://jira.codehaus.org/browse/MJAR-140
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.3.1
Reporter: Eran Harel
I migrated maven to version 3.0.1 in order to utilize the parallel build
experimental feature.
As a result I get the following warning:
{code}
[WARNING] *
[WARNING] * Your build is requesting parallel execution, but project *
[WARNING] * contains the following plugin(s) that are not marked as *
[WARNING] * @threadSafe to support parallel building. *
[WARNING] * While this /may/ work fine, please look for plugin updates*
[WARNING] * and/or request plugins be made thread-safe. *
[WARNING] * If reporting an issue, report it against the plugin in*
[WARNING] * question, not against maven-core *
[WARNING] *
[WARNING] The following plugins are not marked @threadSafe in DataBuilder:
[WARNING] org.apache.maven.plugins:maven-eclipse-plugin:2.8
[WARNING] org.apache.maven.plugins:maven-jar-plugin:2.2
[WARNING] *
{code}
I upgraded the maven-jar-plugin to the latest version (2.3.1), and the
message is gone, but now the builds take much longer: minutes added!!!
The build takes about x 1.5 longer now.
I also compared the maven 3 parallel build time with the new jar-plugin VS a
serial build with the old 2.2 plugin version I had. The results are that
same, while when using the parallel build with the 2.2 plugin I see a
significant ~30% performance boost.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
