Hi Ankit, Thank you for this summary. I look forward to seeing the results of the new study!
If possible, it would be great to see results with different resource allocations on the frontend and backend. This would help with capacity planning. For example: * X-small, Small, Medium, Large Fineract 1.x containers can support X concurrent users with response times under Y * X-small, Small, Medium, Large MySQL instance can support X concurrent requests with Y total records Also, if you provide the test scripts in a consumable format, these tests can be repeated for more types of infrastructure and kept up to date. I cannot commit to timelines right now, I would like to be able to run your tests on AWS. Samuel Hjelmfelt Chief Technology Officer Trellis Housing Finance Limited<https://trellisfi.com/> From: Ankit Muellner <[email protected]> Sent: Tuesday, July 14, 2020 8:25 AM To: [email protected]; Mifos software development <[email protected]> Cc: Ed Cable <[email protected]> Subject: Announcing a Scalability and Performance benchmark test Hi all, In wide variety of Performance and Scalability Studies conducted over last 5 years, following are the aspects reported: In a 2015 study, it has been found that: 1. Platform can support over 3000 virtual users on a single server with mean login times under 2000ms. 2. Platform's client management easily supports 3000 users while accessing client profile from 4,910,000 clients in the clients management system 3. Platform's client management easily supports 3000 users while accessing loan profiles from 20M loans in the LMS module 4. Platform can handle 2800 concurrent repayments with mean response time of 3500ms. 5. Given sufficient database resources and efficient load balancing, platform can scale linearly as one adds additional servers to a cluster. Citation: Conflux Mifos Partner In a 2017 study, it has been found that: 1. The platform when run by 1500 users executed 8.8 throughput(requests processed per second by the test server) with a Std. deviation of 14538.84 and an error margin of 39.73% for one user. 2. Further, the study suggests that 1332.2 bytes of average date of the application is a generic output with 11.52 KB/sec of application data. 3. It is also reported that of the 1500 HTTP requests, 904 are OK, 570 timed out and 19 were Reset by the platform. Remaining are reported as multiple type of errors such as 443: failed to respond. Citation: Esolve There have not been any new study reported to the community. Of course there are Hosting experiences from partners. We are planning a newer 2020 benchmark study with our case study partners- both are leading FIs in their industry by Sept this year. We are planning to use IBM cloud infrastructure and including containerization aspects in this study. We will be releasing it to support community documentation. This will cover CN & 1.x. Anyone would like to participate or comment over this thread on the factors to consider? Is there a study which a partner has performed but not reported? -- Ankit Müllner Muellners Europe +4581929792 Sent from my iPad. This mail is governed by Muellners® IT policy. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
