Performance Testing
Performance testing for Mifos began in earnest in response to the rapid growth of MFI Grameen Koota. As of September 2010, we now continuously execute performance tests using a EC2 test lab.
Strategy
Details of the scalablity/performance testing strategy. Also see attached documents for details on managing Hudson, the purpose of the Hudson jobs, and creating a new AMI on EC2.
Performance Tests
Test data: As of Sept 2010, executing tests with test database that has 2 million clients.
Test Name |
Description |
Measurement |
|---|---|---|
Collection Sheet Entry - 1 user |
Test submit time for collection sheet while no other users are submitting collection sheets. |
Avg. time from submit on Collection Sheet Entry until success page appears |
Collection Sheet Entry - 10 users |
Test submit time for collection sheet while 10 other users are submitting collection sheets. |
Avg. time from submit on Collection Sheet Entry until success page appears |
Collection Sheet Entry - 30 users |
Test submit time for collection sheet while 30 other users are submitting collection sheets. |
Avg. time from submit on Collection Sheet Entry until success page appears |
Login |
Test the response time for a single user's login while 10 other simultaneous logins occur. |
Avg. time from submit on login page until home page appears |
Loan account search |
Test the response time for a single user's search while other simultaneous searches occur. |
Avg. time from clicking search button until loan account appears |
Client Creation |
Test the response time for a single user to create a client while other simultaneous client creations occur. |
Avg. time from submitting form to add client until client created page appears |
Performance Test Results
Performance lab's instances have been terminated at August 26th. If you want the latest performance test results, please contact Mifos developers mailing list.
Next Enhancements
* Email notifications when results are above or below defined thresholds
* add more performance tests