[
https://issues.jenkins-ci.org/browse/JENKINS-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158549#comment-158549
]
Timothy Bingaman commented on JENKINS-12638:
--------------------------------------------
The second part of that ({{O(xn)}}) can't be helped, but the first part
({{O(x^2)}}) is horribly inefficient.
Using the solution that was applied to the Maven Plugin for [JENKINS-7535] in
commit
[6a5330fd936fb949da74d738b82dcf5333282b61|https://github.com/jenkinsci/jenkins/commit/6a5330fd936fb949da74d738b82dcf5333282b61]
this first part can be reduced roughly to an {{O\(n\)}} operation, resulting
in a final order of about {{O(n + xn)}}.
> Rebuilding dependency graph slow on large numbers of Ivy Projects
> -----------------------------------------------------------------
>
> Key: JENKINS-12638
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12638
> Project: Jenkins
> Issue Type: Bug
> Components: ivy
> Reporter: Timothy Bingaman
> Assignee: Timothy Bingaman
>
> Similar issue to [JENKINS-7535], but in the Ivy Plugin instead of the Maven
> Plugin.
> Every time a project is saved, Jenkins rebuilds the dependency graph.
> For Ivy Projects this includes building up a dependency map of all the Ivy
> modules in Jenkins and then applying the build triggers based on that
> information. Currently, this is being done in every single module resulting
> in an operation which is roughly in the order of {{O(n^2 + xn)}} where {{n}}
> is the number of Ivy modules in Jenkins and {{x}} is the average number of
> direct dependencies each module has.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
