Hey, as far as I know EHCache is used to enable 2nd levelcache for Hibernate, so a per node cache. If we want upfront distributed caching I'd vote forHazelcast, because we'd need to implement it anyways. I back Keith' question, it would be good to know whatthe issue is to understand the needed adjustments. Is the bottleneck on the service side, is it DB related,or maybe the network. Where we loose performance here?
Best, Markus .::YAGNI likes a DRY KISS::. > Date: Thu, 7 Apr 2016 10:04:16 +0100 > Subject: Re: [jira] [Updated] (FINERACT-135) Performance improvement using > EHCache or any other cache managers > From: [email protected] > To: [email protected] > > Binny, > > >> In a production environment wiith about 130,000 clients with loans - the > performance of the loan APIs are poor. > > This statement is too vague. What functionality of loans is said to have > poor performance. Is it the fetch part of loans of the transactions that > happen over the loans like make payment etc which if I remember interact > closely with the Accounting area. Is accounting turned on/configured when > performance is poor? Is it 'synchronously' coupled to the loans > functionality as part of loan transactions. > > Caches will only help on the GET/Fetch side of things. > > Is distributed caching supported on Mifos using EHcache or is it just > single node cache? Some like Hazelcast or similiar might be a good option > if wanting to support distributed caching. > > regards, > Keith. > > On Thu, Apr 7, 2016 at 9:57 AM, Binny Gopinath Sreevas (JIRA) < > [email protected]> wrote: > > > > > [ > > https://issues.apache.org/jira/browse/FINERACT-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > Binny Gopinath Sreevas updated FINERACT-135: > > -------------------------------------------- > > Description: > > In a production environment wiith about 130,000 clients with loans - the > > performance of the loan APIs are poor. I have been told is that enabling > > EHCache and making it work will definitely improve the performance. Can > > this be done and tested for deployment scenarios - including multi-tenant > > setup and load balanced (multiple tomcats/FINERACT instances which talk to > > the same database). > > > > Reference to previous work on this: > > > > https://mifosforge.jira.com/wiki/display/projects/GSOC+2013+-+Distributed+Caching+support > > > > was: > > In a production environment wiith about 130,000 clients with loans - the > > performance of the loan APIs are poor. I have been told is that enabling > > EHCache and making it work will definitely improve the performance. Can > > this be done and tested for deployment scenarios - including multi-tenant > > setup and load balanced (multiple tomcats/FINERACT instances which talk to > > the same database). > > > > > > > > > > > Performance improvement using EHCache or any other cache managers > > > ----------------------------------------------------------------- > > > > > > Key: FINERACT-135 > > > URL: https://issues.apache.org/jira/browse/FINERACT-135 > > > Project: Apache Fineract > > > Issue Type: Improvement > > > Reporter: Binny Gopinath Sreevas > > > Assignee: Markus Geiss > > > Priority: Critical > > > > > > In a production environment wiith about 130,000 clients with loans - the > > performance of the loan APIs are poor. I have been told is that enabling > > EHCache and making it work will definitely improve the performance. Can > > this be done and tested for deployment scenarios - including multi-tenant > > setup and load balanced (multiple tomcats/FINERACT instances which talk to > > the same database). > > > Reference to previous work on this: > > > > > https://mifosforge.jira.com/wiki/display/projects/GSOC+2013+-+Distributed+Caching+support > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332) > >
