Mailing-List: contact xalan-j-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID;
  b=hR2kdOO2Qnvy9QHSl1gUXNNEOorKau71LFzSJ/0vX4eI8DcFlrYUOTrQST275ic41T784SJQua+8OXbwuiOh1WMTRzvGI1bhzoZrpwe1YHV6ppwKOTMQ+hmePZklJeedTQEW2DD/FyusI7eeeoC4PmYnb0mGpxIY6lcoxWA24XU=;
Date: Tue, 16 Sep 2008 11:17:38 -0700 (PDT)
From: Tatu Saloranta <cowtowncoder@yahoo.com>
Reply-To: cowtowncoder@yahoo.com
Subject: Re: XSL Transformation in Xalan - Pls help!
To: xalan-j-users@xml.apache.org
In-Reply-To: <7870f82e0809161009i29984899ncd0b7fad0ba31456@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <695107.79723.qm@web32804.mail.mud.yahoo.com>

--- On Tue, 9/16/08, Mukul Gandhi <gandhi.mukul@gmail.com> wrote:

...
> I am still curious why do you want to make stylesheet
> runtime even
> better than 700 ms (on Linux) (which is < 1 sec. I can
> blink my eyes
> in 1 sec :)).

Well, if this is on server-side processing, 700 msec along is dead slow, even service-stopping slow for typical request processing. :-)

I mean, 1.5 transactions per second per core is two orders of magnitude from what most services would want to see (at least ones I've worked with).
At least considering it's a cpu-intensive task not dependant on external resources.

Of course 0.7 seconds may be just fine for batch-processing or client-side. But for most web services it'd be too slow.

As to platform differences, locking is one area where platform/OS does matter. So if and when there are differences, that could explain it.
Otherwise it does seem odd indeed that cpu intensive task performance was asymmetrics between linux and windows.

-+ Tatu +-