Hi Samisa, We need to run the test again to answer that. Will run it again and give an update.
Regards Asanthi On Wed, Aug 6, 2014 at 2:21 PM, Samisa Abeysinghe <[email protected]> wrote: > > > On Wed, Aug 6, 2014 at 2:10 PM, Asanthi Kulasinghe <[email protected]> > wrote: > >> Hi, >> >> We did a long running test with throttling enabled. >> A 100% CPU usage on a key manager node was noticed. >> > > Does this usage go down when we kill the load? > > >> We are yet to analyze the results. >> > > > >> >> >> The current AM171 setup being tested is as follows : >> >> 1. Publisher >> 2. Store >> 3. Gateway cluster with a hybrid node and a worker node fronted by the ELB >> 4. Key Manager cluster with 2 worker nodes fronted by the ELB >> >> - Auth Manager configurations of publisher and store nodes are pointed to >> IS. >> - SSO is enabled among store and publisher >> >> Regards >> Asanthi >> >> >> >> On Tue, Aug 5, 2014 at 12:46 PM, Nuwan Dias <[email protected]> wrote: >> >>> Hi, >>> >>> Thanks for the report. Asanthi its good we can get going on the long >>> running tests as well. We should specifically test for memory consumption, >>> spinning threads, etc. Make sure that you do these tests with throttling >>> enabled. >>> >>> Thanks, >>> NuwanD. >>> >>> >>> On Tue, Aug 5, 2014 at 12:40 AM, Asanthi Kulasinghe <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> The current status of the AM1.7.1 test is as follows. >>>> >>>> 1) AM1.7.1 specific issue fixes have been verified except for the >>>> following. >>>> >>>> https://wso2.org/jira/browse/APIMANAGER-983 >>>> https://wso2.org/jira/browse/APIMANAGER-2482 >>>> https://wso2.org/jira/browse/APIMANAGER-2590 >>>> >>>> Please refer to [1] to view the status of AM1.7.1 issue verification >>>> and reopened issue list. >>>> >>>> 2) Performance and migration tests are ongoing and the following >>>> blockers have been reported for migration scenarios. >>>> >>>> https://wso2.org/jira/browse/APIMANAGER-2698 >>>> https://wso2.org/jira/browse/APIMANAGER-2662 >>>> >>>> Refer to [2] to view a complete list of issues reported. >>>> >>>> 3) The following issues have been fixed but the fixes are not available >>>> in the latest pack. Therefore it's better if we could have a new pack and a >>>> p2repo at your earliest. >>>> >>>> https://wso2.org/jira/browse/APIMANAGER-2657 >>>> https://wso2.org/jira/browse/APIMANAGER-2667 >>>> https://wso2.org/jira/browse/APIMANAGER-2541 >>>> >>>> >>>> [1] >>>> https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AqHAQ3Oa5kRHdG81T3B1QWpLblZXdXlvM0VBQlAyc2c&pli=1#gid=105 >>>> >>>> [2] https://wso2.org/jira/issues/?filter=11929 >>>> >>>> >>>> Regards >>>> *Asanthi Kulasinghe* >>>> WSO2 Inc; http://www.wso2.com/. >>>> Mobile: +94777355522 >>>> >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> *Asanthi Kulasinghe* >> WSO2 Inc; http://www.wso2.com/. >> Mobile: +94777355522 >> >> >> > -- *Asanthi Kulasinghe* WSO2 Inc; http://www.wso2.com/. Mobile: +94777355522
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
