After load testing an application with Locust, the ldap_user module saveAccount method on each login was causing a very large performance hit. Two screen shots have been attached showing the load caused by the account save.
Set up a load test using Locust, jMeter etc, and hit the application for around 6000 users with a spawn rate of 6, you should see a bottleneck begin to form when updating the account.
Only update the account if a change is detected.
Possibly refactor the provided patch.
Account save only to change when the account changes.
Postponed
4.0
Code
Here is a patch and a snapshot of the load test results after adding the change.
I will consider adding this after there is sufficient test coverage. I don't know what 'gremlins' are hiding in the untested code.