[
https://issues.apache.org/jira/browse/BROOKLYN-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666313#comment-15666313
]
ASF GitHub Bot commented on BROOKLYN-382:
-----------------------------------------
Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/423
The commit `EntityExecutionManagerTest: tidy` is because
`org.apache.brooklyn.core.mgmt.internal.EntityExecutionManagerTest.testGcTaskAtNormalTagLimit`
failed in the jenkins PR build. But I can't reproduce that, and I don't have
the full stacktrace unfortunately.
> Catalog takes long time to load in web-console
> ----------------------------------------------
>
> Key: BROOKLYN-382
> URL: https://issues.apache.org/jira/browse/BROOKLYN-382
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 0.9.0
> Reporter: Aled Sage
>
> Using Brooklyn 0.10.0-SNAPSHOT (but also reproducible with 0.9.0)...
> When there are many (yaml) catalog items, the Brooklyn web-console is very
> slow to show the "add application" dialog, or to show a list of the catalog
> items in the catalog view.
> Looking at the REST api timings, the bulk of the time is spent calling
> {{/catalog/entities}} and/or {{/catalog/applications}}.
> A customer with approximately 100 (large) things in their catalog reported
> that it took 15 seconds to show the "add application" dialog. In my testing
> with approx 100 small catalog items, it took approx 5 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
