[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Load testing bind performance
- To: Tim <tim@yetanother.net>, openldap-technical@openldap.org
- Subject: Re: Load testing bind performance
- From: Howard Chu <hyc@symas.com>
- Date: Wed, 1 Nov 2017 19:19:29 +0000
- In-reply-to: <WM!fefae59b007aac47daa714f1fe2b7363558e3a2de70e9ea18966fa3d278aaa9f63328117170adeb6e6e3fa7be2d3a85a!@mailstronghold-1.zmailcloud.com>
- References: <CAPkXO3Upv=L+fmYtgMi5sz+HF3jyBvS5236JkRycKxHNkshd3A@mail.gmail.com> <WM!fefae59b007aac47daa714f1fe2b7363558e3a2de70e9ea18966fa3d278aaa9f63328117170adeb6e6e3fa7be2d3a85a!@mailstronghold-1.zmailcloud.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53a1
Tim wrote:
Heya,
Could anyone recommend a quick and dirty way in which to load test an OpenLDAP
service to get an indication as to the potential capacity for the platform to
handle bind requests?
I've used the python-ldap library to simulate other varieties of interactions
successfully, but when it comes to binds, each interaction seems to generate a
substantial amount of traffic behind the scenes, so suspect that *things* are
happening that is artificially limiting the bind rate/s.
I've seen some links to people using JMeter to perform this sort of load
testing, but thought there may be other (quicker to implement) tools also?
You can look at slapd-bind and slapd-auth in the OpenLDAP test suite, that's
what they're for.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/