Re: [wtp-incubator-dev] XSLT Profiling

[Stuart Harper <stuartharper@xxxxxxxxx>]

Doug,

I didn't raise a bug because it wasn't clear if this was an issue specific to me/my setup or not.

Having the Java information available sounds like a good idea - memory usage in particular tends to be ignored when using XSLT until the stack heap blows!

On Wed, Apr 8, 2009 at 9:41 AM, Doug Satchwell <doug.satchwell@xxxxxxxxx> wrote:

Stuart, did you raise a bug for this?

I remember actually putting profiling there on purpose, with the intention of implementing it.

All I was going to do was to allow the Java based processors to be profiled as regular Java programs, so you can see how much memory is used etc. This is useful information that might sway you towards Saxon over Xalan for instance, for particular transformations.

I'll raise a bug for that enhancement.

Doug

----- Original Message ----
> From: David Carver <d_a_carver@xxxxxxxxx>
> To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
> Sent: Tuesday, 3 March, 2009 21:34:27
> Subject: Re: [wtp-incubator-dev] XSLT Profiling
>
> Stuart Harper wrote:

> > On Tue, Mar 3, 2009 at 9:14 PM, David Carver > > wrote:
> >
> > Is it actually possible to profile XSLs via the transformer interfaces? I've
> never worked with Xalan or Saxon at that level.
> Technically you could hook in a profiler, as Xalan tossed the necessary events
> for when it hits Templates, called-templates, nodes, statements etc.  So you
> could get some information on how long it is spending in particular templates,
> etc.
>
> I've seen profilinging implemented in other commercial products that use Xalan
> and Saxon.
>
> Dave
>
>
> _______________________________________________
> wtp-incubator-dev mailing list
> wtp-incubator-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev





_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev