Great! Thanks Anjana! On Wed, Jun 15, 2016 at 11:26 AM, Anjana Fernando <[email protected]> wrote:
> Hi, > > We've added the $subject. Basically, a local cache is now maintained in > each event table, where it will store the most recently used data items in > the cache, up to a certain given cache size, for a maximum given lifetime. > The format is as follows:- > > @from(eventtable = 'analytics.table' , table.name = 'name', *caching* = > 'true', *cache.timeout.seconds* = '10', *cache.size.bytes* = '100000') > > The cache.timeout.seconds and cache.size.bytes values are optional, with > default values of 60 (1 minute) and 1024 * 1024 * 10 (10 MB) respectively. > > Also, there are some debug logs available in the component, if you want to > check for explicit cache hit/miss situations and record lookup timing, > basically enable debug logs for the class > "org.wso2.carbon.analytics.eventtable.AnalyticsEventTable". > > So basically, if you use analytics event tables in performance sensitive > areas in your CEP execution plans, do consider using caching if it is > possible to do so. > > The unit tests are updated with caching, and the updated docs can be found > here [1]. > > [1] > https://docs.wso2.com/display/DAS310/Understanding+Event+Streams+and+Event+Tables#UnderstandingEventStreamsandEventTables-AnalyticseventtableAnalyticseventtable > > Cheers, > Anjana. > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- Thanks & regards, Nirmal Team Lead - WSO2 Machine Learner Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
