[
https://jira.codehaus.org/browse/MENFORCER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milos Kleint updated MENFORCER-213:
-----------------------------------
Attachment: enforcer-1.3.1.png
enforcer-1.1.png
and the 2 updated screenshots that show the same methods in 1.1 and 1.3.1.
Please note that the atlassian specific rule is the same as the regular ban
snapshots rule but bans also milestones and release candidate dependencies.
But it should be obvious from the snapshots that no excessive time is spent in
atlassian specific rule code, but in the shared
AbstractBanDependencies.getDependenciesToCheck() call.
> big performance degradation after upgrade from 1.1 to 1.3.1
> -----------------------------------------------------------
>
> Key: MENFORCER-213
> URL: https://jira.codehaus.org/browse/MENFORCER-213
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.3.1
> Environment: mvn 3.0.5, MacOsX yosemite, SSD disk
> Reporter: Milos Kleint
> Attachments: 2014-11-13_0851.png, 2014-11-13_0852.png,
> enforcer-1.1.nps, enforcer-1.1.png, enforcer-1.3.1.nps, enforcer-1.3.1.png
>
>
> mvn validate on our big codebase (142 modules) with 1.1 enforcer - 30.090s
> mvn validate with (1.3.1 enforcer) - 2:20.074s
> only enforcer plugin executions happen, bannedDependencies rules
> both times are on my laptop with profiler snapshot collection turned on.
> with the 1.3.1 it's obvious that the majority of time is indeed spent in the
> dependency graph codebase that is missing from 1.1.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
