Emmanuel Lecharny wrote:
...
* 2.0-RC1 + patch
You probably meant RC2 here.
...
This is a very simple test, done with Jmeter : Bind, search N times
the same user, and unbind. Usually, N * nbthreads = 5 000
Here are what I get :
* 0.8 : unstable. I was able to do around 236 search request per
second, with one thread, and I hve got many error.
* 0.9 : Strange enough, the fastest of all the different versions : I
reached 744 searches per second with 5 threads.
With correctness comes a cost ... various schema checks and such are
slowing down the server.
* 0.9.1 : not tested yet
* 0.9.2 : Impossible to do some tests with more than one thread. Peak
at 555 searches per second.
* 0.9.3 : Same problem than 0.9.2. I got 469 req/s
* 1.0-RC1 : a peak at 566 req/s. Performance degradation after a few
seconds : there is a memory leak.
* 1.0-RC1 + patch : more than 780 req/s with one thread. No more
memory leak. *But* : just freeze with more than one thread, after a
few thousand requests. There is a concurrent access problem in this
version...
Shooot! We have to find this concurrency issue. :(
Ok, it was just to inform you, developpers and users, about which
kind of performance we can expect from ADS, and also which kind of
problems we are facing. Obviously, 1.0-RC1 is *not* production ready.
And 1.0-RC2 is still in its pre-infancy.
Aahhha!
Alex
