Thats what my question was about. Thanks Azeez. Thanks & Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729
On Wed, Aug 7, 2013 at 5:28 PM, Afkham Azeez <[email protected]> wrote: > > > > On Wed, Aug 7, 2013 at 2:59 PM, Danushka Fernando <[email protected]>wrote: > >> Hi, >> Just wondering about the update mechanism. What happens when original >> value or L2 cache value get updated? >> > > I think the question is, if the L2 (distributed) cache got updated from > another node, how does it get reflected in the L1 caches of the other > nodes. We register an entry listener for the L2 cache, and whenever there > is a change, this gets triggered, and updates the L1 caches as well. > > >> >> Thanks & Regards >> Danushka Fernando >> Software Engineer >> WSO2 inc. http://wso2.com/ >> Mobile : +94716332729 >> >> >> On Wed, Aug 7, 2013 at 2:02 PM, Afkham Azeez <[email protected]> wrote: >> >>> [image: Inline image 1] >>> >>> >>> On Wed, Aug 7, 2013 at 11:31 AM, Afkham Azeez <[email protected]> wrote: >>> >>>> While running certain scenarios during testing of the Carbon 4.2.0 >>>> packs, we saw certain performance issues when distributed Hazelcast >>>> HashMaps are used as the backing data structure. To overcome this, I have >>>> introduced the concept of an L1 local cache. It is a write through cache, >>>> where items stored in it will also get written to the distributed data >>>> structure. When there is a L1 cache miss, we will check in the L2 >>>> distributed cache to see whether the value is there. >>>> >>>> I am seeing significant performance improvement in the tenant creation >>>> scenario after this improvement. >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* >
<<caching.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
