[
https://issues.apache.org/jira/browse/AMBARI-20262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892666#comment-15892666
]
Hudson commented on AMBARI-20262:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6915 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6915/])
AMBARI-20262 - Startup Annotation Scanning Takes Too Long (part2) (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f8fe522b95166f18b93135a7b8cd7ff24d1f0fd9])
* (edit)
ambari-funtest/src/test/java/org/apache/ambari/funtest/server/orm/InMemoryDefaultTestModule.java
> Startup Annotation Scanning Takes Too Long
> ------------------------------------------
>
> Key: AMBARI-20262
> URL: https://issues.apache.org/jira/browse/AMBARI-20262
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20262.patch
>
>
> Currently, Ambari uses Spring's
> {{ClassPathScanningCandidateComponentProvider}} along with an
> {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
> ClassPathScanningCandidateComponentProvider scanner =
> new ClassPathScanningCandidateComponentProvider(false);
> // match only singletons that are eager listeners
> for (Class<? extends Annotation> cls : classes) {
> scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
> }
> beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time
> to roughly 8 seconds by switching over to Google's {{ClassPath}} via our
> internal {{ClasspathScannerUtils}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
