Chad Johnson wrote:
>
> Hey,
> Yes, currently I am parsing the stylesheet every page view. Just a note
> of clarification. When I say '1s execution time' I'm talking about the
> total time the application takes to fire up, do the transform, then stop.
>
> What methods would you suggest to skip the translation step every page
> view?
Use the TRAX API to its fullest. If you get a Templates object from your
source XSL, and use that to get an instance of the Transformer, you lose
the overhead of reparsing the stylesheet every time.
>
> I gave XSLTC a whirl. And while working with the translet was faster,
> and less CPU intensive it was still was by no means sleek (50% cpu
> spike).
>
> Another route I could see would be to 'cache' the Transformer in a
> bean.....
>
> Thanks for the input.
>
> -Chad
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> Sent: Thursday, August 16, 2001 6:27 AM
> To: [EMAIL PROTECTED]
> Subject: Java XSLT performance question
>
> Are you parsing the stylesheet with each page view? This will cause the
> delay.
>
> I don't think it's the fastest but I'm doing fairly complex transforms in
> ~
> .1s on a similar box
>
> Al
>
> http://xml.apache.org/xalan-j/usagepatterns.html#embed
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail: [EMAIL PROTECTED]
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
