Also let's publish these stats publicly - just like ESB records it's TPS for different adaptors. Kasun/Inosh can you guys come with comprehensive benchmark plan and get us solid stats. Also the stats has to be in a way that another person can replicate our benchmark results. We'll probably have to mention the devices as well.
Cheers~ On Mon, May 5, 2014 at 11:56 PM, Dilshan Edirisuriya <dils...@wso2.com>wrote: > Hi Kasun/Inosh, > > I think this is a relative problem which depend on the OS version and also > the device type. So what we have to look for the numbers and fine tune to > reduce the memory usage as much as we can. I hope you have used monitor > tool available in Android SDK. From this you can analyze the heap and > allocations. You can get a heap dump of this using the tool. Also you may > look at overall memory allocations as well (private RAM and PSS). More info > found here at [1]. By doing these tests against different devices and > different OS versions can lead to different results. So please analyze them > for different scenarios and comeup with some statistics. > > [1] - https://developer.android.com/tools/debugging/debugging-memory.html > > Regards, > > Dilshan > > > On Mon, May 5, 2014 at 7:29 PM, Kasun Dananjaya Delgolla > <kas...@wso2.com>wrote: > >> Hi Dilshan, >> >> Actually I have already tested the app for the 2nd and 3rd options that >> you have mentioned. So I think if Inosh can test the 1st scenario, that >> would complete the test. One more that can be checked is the async tasks >> and whether they are destroyed properly once the task is done. >> >> Thanks >> On 5 May 2014 15:20, "Dilshan Edirisuriya" <dils...@wso2.com> wrote: >> >>> Hi Inosh, >>> >>> Can we have a detailed analysis with numbers. Please concentrate on >>> these scenarios. >>> >>> 1) Change policy monitoring time to atleast 1 minute and test its >>> consumption. >>> 2) Do few device operations within few seconds and analyze its results. >>> 3) Run the application for 24 hours and see its overall consumption(you >>> may compare with other apps as well) within 1 battery charge cycle. >>> >>> You may do above with debug on/off and compare the results as well. >>> >>> Regards, >>> >>> Dilshan >>> >>> >>> >>> On Mon, May 5, 2014 at 2:06 PM, Inosh Perera <ino...@wso2.com> wrote: >>> >>>> Hi All, >>>> I'm working on performance optimization of our Android client app (MDM >>>> agent), since some customer's have reported it consumes more than 10% >>>> battery sometimes. Reason seems to be, our app has debug mode enabled, so >>>> over time, the log becomes too big. >>>> >>>> Thanks, >>>> Inosh >>>> >>>> -- >>>> Inosh Perera >>>> Software Engineer, WSO2 Inc. >>>> Tel: 0785293686 >>>> >>> >>> >>> >>> -- >>> Dilshan Edirisuriya >>> Senior Software Engineer - WSO2 >>> Mob: + 94 777878905 >>> http://wso2.com/ >>> >> > > > -- > Dilshan Edirisuriya > Senior Software Engineer - WSO2 > Mob: + 94 777878905 > http://wso2.com/ > -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com <duli...@wso2mobile.com>* * ~Mobile +94712112165* * ~Website dulitha.me <http://dulitha.me>* * ~Twitter @dulitharw <https://twitter.com/dulitharw>* *~Github @dulichan <https://github.com/dulichan>* *~SO @chan <http://stackoverflow.com/users/813471/chan>*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
