Asiri could build on top of my changes, I suppose?
On Tue, Apr 29, 2014 at 10:15 PM, Lahiru Sandaruwan <[email protected]>wrote: > > > > On Tue, Apr 29, 2014 at 9:52 PM, Nirmal Fernando > <[email protected]>wrote: > >> Lahiru, this should be ok right? >> > > Yes. But for 4.1.0, we will be counting the required number of instances > with proposed Gsoc project by Asiri. > >> >> >> On Tue, Apr 29, 2014 at 7:21 PM, Nirmal Fernando >> <[email protected]>wrote: >> >>> 4.1.0 >>> >>> >>> On Tue, Apr 29, 2014 at 12:18 PM, Lahiru Sandaruwan <[email protected]>wrote: >>> >>>> Hi Nirmal, >>>> >>>> Which release do you plan to add this feature? >>>> >>>> Thanks. >>>> >>>> >>>> On Tue, Apr 29, 2014 at 6:08 AM, Nirmal Fernando < >>>> [email protected]> wrote: >>>> >>>>> Hi All, >>>>> >>>>> Current auto-scaler takes only the 'average' threshold value from a >>>>> user's auto-scaling policy. Then inside the scaling related drools rules >>>>> it >>>>> calculates an upper bound and a lower bound by multiplying the average >>>>> threshold value by two non-configurable constants. >>>>> >>>>> scaleUp : Boolean() from ((rifReset && (rifPredictedValue > >>>>> rifAverageLimit * *0.8*)) || (mcReset && (mcPredictedValue > >>>>> mcAverageLimit * 0.8)) || (laReset && (laPredictedValue > laAverageLimit * >>>>> 0.8))) >>>>> scaleDown : Boolean() from ((rifReset && (rifPredictedValue < >>>>> rifAverageLimit ** 0.1*)) && (mcReset && (mcPredictedValue < >>>>> mcAverageLimit * 0.1)) && (laReset && (laPredictedValue < laAverageLimit * >>>>> 0.1))) >>>>> >>>>> IMO this is a limitation and we could make these constants >>>>> configurable via auto-scaling policy. >>>>> >>>>> So, I propose following format to the auto-scaling policy: >>>>> >>>>> { >>>>> "id": "autoscale-policy-1", >>>>> "loadThresholds": { >>>>> "requestsInFlight": { >>>>> "upperLimit": 30, >>>>> "lowerLimit": 5 >>>>> }, >>>>> "memoryConsumption": { >>>>> "upperLimit": 80, >>>>> "lowerLimit": 50 >>>>> }, >>>>> "loadAverage": { >>>>> "upperLimit": 100, >>>>> "lowerLimit": 20 >>>>> } >>>>> } >>>>> } >>>>> >>>>> Then, we can modify the rule to consider user-defined threshold values >>>>> when taking the scaling decision. >>>>> >>>>> Let me know your thoughts. >>>>> >>>>> -- >>>>> Best Regards, >>>>> Nirmal >>>>> >>>>> Nirmal Fernando. >>>>> PPMC Member & Committer of Apache Stratos, >>>>> Senior Software Engineer, WSO2 Inc. >>>>> >>>>> Blog: http://nirmalfdo.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> -- >>>> Lahiru Sandaruwan >>>> Committer and PPMC member, Apache Stratos(incubating), >>>> Senior Software Engineer, >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> email: [email protected] cell: (+94) 773 325 954 >>>> blog: http://lahiruwrites.blogspot.com/ >>>> twitter: http://twitter.com/lahirus >>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Nirmal >>> >>> Nirmal Fernando. >>> PPMC Member & Committer of Apache Stratos, >>> Senior Software Engineer, WSO2 Inc. >>> >>> Blog: http://nirmalfdo.blogspot.com/ >>> >> >> >> >> -- >> Best Regards, >> Nirmal >> >> Nirmal Fernando. >> PPMC Member & Committer of Apache Stratos, >> Senior Software Engineer, WSO2 Inc. >> >> Blog: http://nirmalfdo.blogspot.com/ >> > > > > -- > -- > Lahiru Sandaruwan > Committer and PPMC member, Apache Stratos(incubating), > Senior Software Engineer, > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > email: [email protected] cell: (+94) 773 325 954 > blog: http://lahiruwrites.blogspot.com/ > twitter: http://twitter.com/lahirus > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 > > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
