Hi On Tue, Jun 23, 2015 at 12:50 PM, Gayan Gunarathne <[email protected]> wrote:
> Hi Reka, > > On Tue, Jun 23, 2015 at 12:20 PM, Reka Thirunavukkarasu <[email protected]> > wrote: > >> Hi >> >> While testing found out that we are using different pool for different >> purposes like application monitor, group monitor, cluster monitor and etc. >> Is it possible to use one thread pool per component such as autoscaler with >> higher pool size like 100. Then we can make sure that there will always be >> threads available to do the job whenever needed. WDYT? >> > > +1. Good suggestion. It is important to maintain the component vise thread > pools.I guess we are already doing this with cloud controller. > Thanks. This was actually suggested by Imesh when finding out issues with locks in the undeployment. Thanks Imesh for the good suggestion. > > >> Would you find any issues with merging all the different pools in >> autoscaler to just with one thread pool? >> > > AFAIR we won't have issues by using the thread pool per component. BTW we > need pass the component thread pool for each monitors. > Then great. Will start doing this.. Thanks, Reka > > >> Thanks, >> Reka >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> Thanks, > Gayan > > > -- > > Gayan Gunarathne > Technical Lead, WSO2 Inc. (http://wso2.com) > Committer & PMC Member, Apache Stratos > email : [email protected] | mobile : +94 766819985 > > > -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
