GitHub user aledsage opened a pull request:

    https://github.com/apache/brooklyn-server/pull/736

    Test performance/scalability of many entities

    See individual commits for minor changes / improvements to our 
`AbstractPerformanceTest` support, which builds up to adding the 
`ScalabilityPerformanceTest`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aledsage/brooklyn-server 
test-performance-many-entities

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-server/pull/736.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #736
    
----
commit bfc66f7f352690605ffeb03b6146a13e969f1bfd
Author: Aled Sage <[email protected]>
Date:   2017-06-06T10:20:35Z

    Test tear-down: limit number of threads in Entities.destroyAll
    
    In stress/scale tests that create 1000s of apps, trying to stop them 
    all concurrently with a thread per app causes an OutOfMemoryError
    due to too many threads.

commit ffd799eba6f5768383f1fe651515d39450a2f942
Author: Aled Sage <[email protected]>
Date:   2017-06-06T10:21:25Z

    AbstractPerformanceTest to extends BrooklynAppUnitTestSupport

commit 3f36a298e71027bdb3f92b6ba0425a8c98020c7a
Author: Aled Sage <[email protected]>
Date:   2017-06-06T10:21:57Z

    Performance tests: support numConcurrentJobs

commit 9f758bf5b5678c5480299b97a564e46264a6148c
Author: Aled Sage <[email protected]>
Date:   2017-06-06T12:01:21Z

    Performance test: add options.postWarmup

commit 06f5aac520c5504fe899710e3cc3a28c09e46cc5
Author: Aled Sage <[email protected]>
Date:   2017-06-06T12:02:04Z

    Performance test: add abortIfIterationLongerThan
    
    (And log partial results if fails)

commit dc74f72886d652a672fa35ee2dd6be973b18c549
Author: Aled Sage <[email protected]>
Date:   2017-06-06T10:22:20Z

    Add scalability test for many entities

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to