Hi Suho, Sure, I will look into it.
Thanks. Thilini On Thu, Jul 7, 2016 at 2:08 AM, Sachith Withana <[email protected]> wrote: > Thanks Suho and Sinthuja. > > This was just a suggestion to improve upon what I experienced :) > > Regards, > Sachith > > On Wed, Jul 6, 2016 at 3:20 PM, Sinthuja Ragendran <[email protected]> > wrote: > >> Hi Sachith, >> >> On Wed, Jul 6, 2016 at 11:19 PM, Sachith Withana <[email protected]> >> wrote: >> >>> Agreed Sinthuja. >>> >>> But what about for a smaller window size (5/10/15 mins)? >>> >> >> Even in this case, I would suggest to persist the result. It makes more >> sense to have the realtime analytics when you want to see seconds wise or >> less than a minute analysis, and rest of the use cases we need to persist. >> And you could persist the data in RDBMS such that when you get a new event, >> you update the old value, therefore data doesn't grow. Ie, if you want to >> maintain every minute wise analysis data, you would end up storing >> 60*24=1440 records. Furthermore, as you are just going to insert one event >> per a minute, I don't think it will add any performance implication as well. >> >> >>> The reason why I bought up this issue is, in my case, I use several real >>> time gadgets. >>> And at the startup, they are all empty for that user until the data gets >>> pushed in. >>> >> >> Yeah, I understand. :) As CEP is in memory engine, if we want to handle >> this situation smoothly even after server crashed, etc IMO we need to >> handle this as above described. >> >> Thanks, >> Sinthuja. >> >> >>> As an end user, I would like to see the last status of the real time >>> analytics when I log in. >>> >>> Thanks, >>> Sachith >>> >>> On Wed, Jul 6, 2016 at 12:09 PM, Sinthuja Ragendran <[email protected]> >>> wrote: >>> >>>> Hi Sachith, >>>> >>>> If the use-case is to display the 1 hour analytics data from CEP, then >>>> IMO the he/she need to simply store the CEP results into a persistence >>>> store (DAS or RDBMS via RDBMS event publisher), and then let the gadget >>>> read from the persistence store. I don't think caching is a good option in >>>> such cases because anyhow if the server crashes due to some reason the data >>>> is not going to be shown. >>>> >>>> Thanks, >>>> Sinthuja. >>>> >>>> On Wed, Jul 6, 2016 at 10:12 PM, Sachith Withana <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> In the dashboard, the real time data is only shown if the user is >>>>> logged into the dashboard at the time of the data is being pushed. >>>>> >>>>> If the data is being pushed every hour, a new user who logs in would >>>>> potentially have to wait up to one hour to see the real time data, and if >>>>> the user refreshes, then has to wait another hour to see the data, and >>>>> would loose the current data completely. >>>>> >>>>> I understand from the CEP perspective it's similar to fire and forget, >>>>> but can't we add some level of caching to prevent this? >>>>> >>>>> Regards, >>>>> Sachith >>>>> -- >>>>> Sachith Withana >>>>> Software Engineer; WSO2 Inc.; http://wso2.com >>>>> E-mail: sachith AT wso2.com >>>>> M: +94715518127 >>>>> Linked-In: <http://goog_416592669> >>>>> https://lk.linkedin.com/in/sachithwithana >>>>> >>>> >>>> >>>> >>>> -- >>>> *Sinthuja Rajendran* >>>> Technical Lead >>>> WSO2, Inc.:http://wso2.com >>>> >>>> Blog: http://sinthu-rajan.blogspot.com/ >>>> Mobile: +94774273955 >>>> >>>> >>>> >>> >>> >>> -- >>> Sachith Withana >>> Software Engineer; WSO2 Inc.; http://wso2.com >>> E-mail: sachith AT wso2.com >>> M: +94715518127 >>> Linked-In: <http://goog_416592669> >>> https://lk.linkedin.com/in/sachithwithana >>> >> >> >> >> -- >> *Sinthuja Rajendran* >> Technical Lead >> WSO2, Inc.:http://wso2.com >> >> Blog: http://sinthu-rajan.blogspot.com/ >> Mobile: +94774273955 >> >> >> > > > -- > Sachith Withana > Software Engineer; WSO2 Inc.; http://wso2.com > E-mail: sachith AT wso2.com > M: +94715518127 > Linked-In: <http://goog_416592669> > https://lk.linkedin.com/in/sachithwithana > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thilini Anoratna* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 778955654 <+94+778955654> * <http://lk.linkedin.com/in/thilinianoratna>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
