Mailing-List: contact xalan-j-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <48CF64B8.5070309@as-guides.com>
Date: Tue, 16 Sep 2008 09:48:08 +0200
From: Michael Ludwig <mlu@as-guides.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: xalan-j-users@xml.apache.org
Subject: Re: XSL Transformation in Xalan - Pls help!
References: <19471054.post@talk.nabble.com>
 <00e801c91741$0c47e080$6401a8c0@MeBigFatGuy> <19494534.post@talk.nabble.com>
In-Reply-To: <19494534.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sriram83 schrieb:
> 1/. We have the XSL transformation taking place inside an application
> deployed in JBOSS app server. There are no restart of JVM.
> Initialisation of memory takes only during jboss startup.

I don't know much about JBoss, but it's a pretty huge application. You
may be testing JBoss instead of Xalan. In order to test Xalan, I'd
rather use a leaner frame, maybe just the simplest of programs which
does what you describe below using loops and timestamps.

> 2/. As mentioned by Tatu, I believe we do allow time for JVM to
> warmup. We run around 200 XSL transformations first, after this, we
> collect the average time taken for around 1000 transactions.

Sounds very reasonable to me.

Michael