Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates
 209.85.220.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=VEVbNTA5VkGMZAaq+fMaN4A7KIiCkXmndCLT+/+77yDKRMDDYR6YXtXddWSZ1Tze7P
         37+nir0f949xxzMAmsjQxmNOUrfUuBNS1B0T5Z8qdfdDFphjS2yXPzseLnJW7+enDwEh
         m5fRNfNm2ANSd6XsIBnhMYeW0SRj8B0bsmSEA=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <fa2d9f450911190057r1cc7fc39ic899113c3a26e978@mail.gmail.com>
References: <fa2d9f450911182327x1066049dvb1e63db824a9114b@mail.gmail.com>
	 <771905290911190012hd4fa7eale77430820238669d@mail.gmail.com>
	 <fa2d9f450911190022s260d5cc8nbcb41036ef0e89f7@mail.gmail.com>
	 <fa2d9f450911190057r1cc7fc39ic899113c3a26e978@mail.gmail.com>
Date: Fri, 20 Nov 2009 14:58:19 +0200
Message-ID: <c7fc82820911200458l649e3492w8998f3dca7dbe13b@mail.gmail.com>
Subject: Re: Performance Tests - Suggestions and Ideas
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I just wanted to say thanks to Markus for doing this, and I think
performance testing is a critical aspect for this type of application
(as Twitter have demonstrated very convincingly).

I also believe performance testing of ESME is also a great way to test
Lift, as ESME is one of the biggest open-source projects using Lift
(ok, there aren't many anyway). Other bugs which performance tests
could catch would be deadlocks and thread contention, and these are
vitally important in the light of the dynamic change Lift is
undergoing swapping its actor implementations.

It's also a good idea to run performance tests on Hudson, at least for
the time being- we don't have that many commits per week yet.

About memory analysis being a low-hanging fruit: agree 100%, provided
one condition is fulfilled. The condition is that we're able to test
the application locally, and performance tests help us do exactly
that. Previously many bugs could only be reproduced by everyone on the
Stax instance. Besides, a long time ago I have worked on memory leak
problems in the same area as Markus, so I think we have enough
know-how.

Vassil