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 markus.kohler@gmail.com
 designates 209.85.210.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=vr8LUXAGwLjigXmVUfJzoYGO60b0V3PuP6QgMbPeqy2tpm1P8CUj1yg5vW6czeg6Zk
         g1cfs+8upm5PcUzoXX+gLDoW6W3ZfihWsgZ3eitDfm2OK80XB/2679wSHKYtmr90hvyi
         xdeFk/t1WH0HT4PJQUDXdCs9Oa6jfygpKXLCU=
MIME-Version: 1.0
In-Reply-To: <c7fc82820911200458l649e3492w8998f3dca7dbe13b@mail.gmail.com>
References: <fa2d9f450911182327x1066049dvb1e63db824a9114b@mail.gmail.com>
	 <771905290911190012hd4fa7eale77430820238669d@mail.gmail.com>
	 <fa2d9f450911190022s260d5cc8nbcb41036ef0e89f7@mail.gmail.com>
	 <fa2d9f450911190057r1cc7fc39ic899113c3a26e978@mail.gmail.com>
	 <c7fc82820911200458l649e3492w8998f3dca7dbe13b@mail.gmail.com>
Date: Fri, 20 Nov 2009 14:23:29 +0100
Message-ID: <771905290911200523gf5d2e76j97fc84727840eb14@mail.gmail.com>
Subject: Re: Performance Tests - Suggestions and Ideas
From: Markus Kohler <markus.kohler@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=001636164a29ac7b630478cd6187

--001636164a29ac7b630478cd6187
Content-Type: text/plain; charset=ISO-8859-1

Hi all,
Just as a teaser ;-)
The textile support is expensive in regards to the memory allocated (freed
afterwards).
Details will come as soon as I find some time.

Regards,
Markus

On Fri, Nov 20, 2009 at 1:58 PM, Vassil Dichev <vdichev@apache.org> wrote:

> 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
>

--001636164a29ac7b630478cd6187--