[
https://issues.apache.org/jira/browse/BROOKLYN-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670188#comment-15670188
]
ASF GitHub Bot commented on BROOKLYN-382:
-----------------------------------------
Github user neykov commented on a diff in the pull request:
https://github.com/apache/brooklyn-server/pull/423#discussion_r88216504
--- Diff: parent/pom.xml ---
@@ -1395,42 +1395,32 @@
</build>
</profile>
<profile>
+ <id>Performance</id>
+ <properties>
+ <includedTestGroups>Performance</includedTestGroups>
+ <excludedTestGroups>Live,WIP,Broken</excludedTestGroups>
+ </properties>
+ </profile>
+ <profile>
<id>Acceptance</id>
<properties>
<includedTestGroups>Acceptance</includedTestGroups>
<excludedTestGroups>Integration,Live,WIP,Broken</excludedTestGroups>
--- End diff --
Why exclude `Performance` in the other groups but not here?
To have the tests which are annotated with two groups to run the of of the
groups should not be excluded from the profile of the other one. But then why
make `Performance` special?
I think we should just exclude `Broken` and let mixed tests execute in
either of the groups.
> 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)
