Hi Sinthuja, I'm seeing around 500MB of memory usage in the DAS 3.1.0-SNAPSHOT "Generate Gadget" page as well, specially when the gadget is being previewed. At that moment, there is only one gadget in play, and the number of records is less than 100.
Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Wed, Jun 29, 2016 at 11:53 PM, Sinthuja Ragendran <[email protected]> wrote: > Hi Chamila, > > I think this is specifically for analytics dashboard right, and not for > simple dashboards? In that case, we need to check how the gadgets have been > written, and because the actual data is being fetched from DAS into this > gadgets, and I believe the fetched data to display in gadget is consuming > more memory. Can you try to delete some gadgets from the above page and see > whether there is an improvement? > > @Dunith/Tharik, Whether data is loaded in paginated manner (ie, not load > all, only load the data which is required for the specific page)? And do we > load events with its all attributes or only with specific attributes we > required to show? I believe we have done some testing for ESB analytics > case right, didn't we hit this sort of issue in our local testing? > > Thanks, > Sinthuja. > > > On Thu, Jun 30, 2016 at 9:19 AM, Nipuna Chandradasa <[email protected]> > wrote: > >> [Adding Udara,Sinthuja, and Tanya] >> >> Hi Chamila, >> >> This much of memory never used by shindig on gadget rendering. Because >> gadgets are pretty simple as i check them. There must be some pre processes >> going on. That might cause this kind of memory usage. >> >> Thank you, >> >> On Thu, Jun 30, 2016 at 1:46 AM, Chamila De Alwis <[email protected]> >> wrote: >> >>> Hi, >>> >>> ESB 5.0.0 beta analytics dashboard seems to be taking a considerable >>> amount of memory to operate. I noticed the following in >>> Chrome 51.0.2704.103 m (64-bit) in Windows. >>> >>> >>> [image: Inline image 2] >>> >>> Next to Gmail Inbox, ESB Dashboard takes about average 400MB to operate. >>> This can sometimes go up to more than 700MB when browsing through pages. >>> >>> I compared the memory usage against Grafana demo, Grafana Playground [1] >>> and a Kibana4 demo[2], which takes average 150MB and 200MB of memory >>> respectively. >>> >>> IMO there's room for this memory usage to be reduced. Since dashboards >>> would likely be used frequently, reducing the memory footprint would add a >>> considerable amount of value to the user experience. >>> >>> [1] - http://play.grafana.org/ >>> [2] - https://kibana.logit.io/app/kibana#/dashboard/Demo-IIS-Dashboard >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Software Engineer | WSO2 | +94772207163 >>> Blog: code.chamiladealwis.com >>> >>> >>> >> >> >> -- >> Nipuna Marcus >> *Software Engineer* >> WSO2 Inc. >> http://wso2.com/ - "lean . enterprise . middleware" >> Mobile : +94 (0) 713 667906 >> [email protected] >> > > > > -- > *Sinthuja Rajendran* > Technical Lead > WSO2, Inc.:http://wso2.com > > Blog: http://sinthu-rajan.blogspot.com/ > Mobile: +94774273955 > > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
