Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of elecharny@gmail.com designates
 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
        b=saJfwY7uKdG+btSbU1WYn4KoA5nA2KjXAmbhOld/CY5oEjNi0hA6h3ytQhWEc6XgJHPfsbEJIjlhNit5f2yaCAadl9NVT8QNyJbE+RgAYHPQYEutQGL2oes0iWw8ddtZQKeeQ+dpKVPkGSAux+hReVqZTZTNOzKN9f7/9h6xaOk=
Message-ID: <d45b08f00703231009w69d2d536h289d4bc596a30c9f@mail.gmail.com>
Date: Fri, 23 Mar 2007 18:09:08 +0100
From: "Emmanuel Lecharny" <elecharny@gmail.com>
Reply-To: elecharny@iktek.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: [Integration tests] How to speed up the tests
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_220647_12721056.1174669748291"

------=_Part_220647_12721056.1174669748291
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

with the new schema handling system (the schema is now stored as Ldap
entries in the server, and loaded at startup), the integration tests are
taking forever (17 mins on my 3GhZ desktop, 13 minutes on my shinny Imac
dual-core).

The reason is that all the schema elements have to be read out of the
server, and as the server is able to manage around 500 req/s (more or less)=
,
each test cost around a second, bare minimum.

As we have around 150 tests in server-unit, this is around 3 minutes to run
integration tests, and we have the double in core-unit, so it's 6 more
minutes.

We have a few options :
1) Improve the server so it can handle 5000 req/s, dividing the tests
duration by ten : yeah, that would be cool, but...
2) Improve the tests to limit the number of server startup and shutdown to
one by test (the setup should contain a test to check if the server has bee=
n
started or not before, and add code to feed the server and some other code
to clean the server)
3) Write a new tool which will register all the operations to play them in
revert order when finishing a test
4) any other smart idea, guys ?

--=20
Cordialement,
Emmanuel L=E9charny
www.iktek.com

------=_Part_220647_12721056.1174669748291
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,<br><br>with the new schema handling system (the schema is now stored as=
 Ldap entries in the server, and loaded at startup), the integration tests =
are taking forever (17 mins on my 3GhZ desktop, 13 minutes on my shinny Ima=
c dual-core).
<br><br>The reason is that all the schema elements have to be read out of t=
he server, and as the server is able to manage around 500 req/s (more or le=
ss), each test cost around a second, bare minimum. <br><br>As we have aroun=
d 150 tests in server-unit, this is around 3 minutes to run integration tes=
ts, and we have the double in core-unit, so it&#39;s 6 more minutes.
<br><br>We have a few options :<br>1) Improve the server so it can handle 5=
000 req/s, dividing the tests duration by ten : yeah, that would be cool, b=
ut... <br>2) Improve the tests to limit the number of server startup and sh=
utdown to one by test (the setup should contain a test to check if the serv=
er has been started or not before, and add code to feed the server and some=
 other code to clean the server)
<br>3) Write a new tool which will register all the operations to play them=
 in revert order when finishing a test<br>4) any other smart idea, guys ?<b=
r clear=3D"all"><br>-- <br>Cordialement,<br>Emmanuel L=E9charny<br><a href=
=3D"http://www.iktek.com">
www.iktek.com</a>

------=_Part_220647_12721056.1174669748291--