Hi Kaushal, Your email provides a great summary of what needs to be done for your load testing on Fineract.
Regarding your question about recommendations, you might want to check out the JMeter Best Practices page: https://jmeter.apache.org/usermanual/best-practices.html Milamber > De : Kaushal Shriyan <[email protected]> > Date: mar. 1 sept. 2026 à 19:34 > Subject: Apache JMeter – Concurrent API Request Load Testing > To: JMeter Users List <[email protected]> > > > Hi, > > We are planning to perform load testing of the Apache Fineract APIs ( > https://fineract.apache.org/) using Apache JMeter, with a focus on > simulating concurrent API requests and evaluating the system's performance > under different load conditions. > > The proposed approach is to configure JMeter to simulate multiple > concurrent users sending requests to the Fineract APIs. We will gradually > increase the number of concurrent users to evaluate response times, > throughput, error rates, and overall system stability. > > The testing process will broadly include: > > - Identify the key Apache Fineract APIs and critical business > transactions to be tested. > - Configure JMeter Thread Groups to simulate multiple concurrent users. > - Configure the number of threads (virtual users), ramp-up period, and > loop count. > - Configure HTTP Request samplers for the required Fineract APIs. > - Configure authentication and authorization as required. > - Parameterize request data to simulate different customers/accounts and > avoid using identical test data. > - Configure listeners and backend monitoring to capture response time, > throughput, and error rates. > - Gradually increase the concurrent user load to identify the system's > performance limits. > - Monitor application server CPU and memory utilization, database > performance, connection pools, and other relevant infrastructure > metrics. > - Analyze the test results and identify potential performance > bottlenecks. > - Document the results and provide recommendations for application, > database, JVM, or infrastructure-level optimizations. > > For example, we can initially test with 50 concurrent users and gradually > increase the load to 100, 250, 500, 1,000, etc., depending on the expected > production workload and available infrastructure. > > Please let us know if there are any recommended concurrency levels, TPS > targets, specific Fineract APIs, or performance benchmarks that should be > considered as part of the testing. > > Best regards, > > Kaushal >
