RE: [xsl] measuring bulk performance & turn around times of XSL t ransformations? ideas for: XML to XML, XML to HTML, XML to FO (then to PD F)

Subject: RE: [xsl] measuring bulk performance & turn around times of XSL t ransformations? ideas for: XML to XML, XML to HTML, XML to FO (then to PD F)
From: Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>
Date: Wed, 28 Apr 2004 10:26:29 -0500
Not necessarily - you could brake up the total transformation into smaller
transformations - so make it a series of transformations (cascading XSLT),
that will allow you to measure time as each transformation progresses, and
has the benefit that your input stays in memory.

HTH,
<prs/>

-----Original Message-----
From: SANWAL, ABHISHEK (HP-Houston) [mailto:abhishek.sanwal@xxxxxx] 
Sent: Wednesday, April 28, 2004 10:20 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] measuring bulk performance & turn around times of XSL
transformations? ideas for: XML to XML, XML to HTML, XML to FO (then to PDF)


True. I believe that would be the simple way. Add 'time' blocks and measure.
But, I was interested in more XSL centric measurements if any, since XSL
does not process XSL code in a top to bottom way like normal code. 

In essence, this will only allow me to measure "total" end to end time and
will not allow me to get other metrics that might be smaller than the
"complete" time.

Of course, I will look into the things suggested by everyone here.
____________________________________________________________

Abhishek Sanwal
HP - Houston Campus
 

-----Original Message-----
From: Pieter Reint Siegers Kort [mailto:pieter.siegers@xxxxxxxxxxx]
Sent: Wednesday, April 28, 2004 10:02 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] measuring bulk performance & turn around times of XSL
transformations? ideas for: XML to XML, XML to HTML, XML to FO (then to
PDF)

No, never used nxslt - I see it is a command line utility using .NET
XslTransform class - interesting!

Of course, N/A means that it's not available or just not implemented.
Anyway, you could contact XSelerator support about that. 

Another option would be to just get the current system time instance when
you start a transformation, and measure time afterwards, in your
application.

What's your take on it?

<prs/>

-----Original Message-----
From: Kenny Akridge [mailto:kenny@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, April 27, 2004 12:55 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] measuring bulk performance & turn around times of XSL
transformations? ideas for: XML to XML, XML to HTML, XML to FO (then to
PDF)

Pieter,

Do you have nxslt running in Xselerator?  If so, have you been able to get
the performance information using it?  I have been unable to so far.  I
always get N/A.

Thanks.

-----Original Message-----
From: Pieter Reint Siegers Kort [mailto:pieter.siegers@xxxxxxxxxxx]
Sent: Tuesday, April 27, 2004 1:50 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] measuring bulk performance & turn around times of XSL
transformations? ideas for: XML to XML, XML to HTML, XML to FO (then to
PDF)

Hi Abhishek,

You could start searching the archives using the word 'performance'. 

Also check http://www.dpawson.co.uk/xsl/sect4/N9883.html. 

> How have you (if ever) measured or tried to measure the performance of

> the
transformations?

Utilities like XSelerator show you the time needed to do when doing XML
parse, XSL parse, and XSL Transformation time. Very useful. I used various
techniques to process XML and compared those times using MSXML 4.0 (you can
use other processors by simply adding them to the Environmental options).

I have been doing some performance testing, but only on two processors sofar
(MSXML 4.0 and .NET's XslTransform). Don't know which you're using?

Cheers,
<prs/>
http://www.pietsieg.com
http://www.pietsieg.com/dotnetnuke
Contributor on www.ASPToday.com
Co-author on "Professional ASP.NET XML with C#", July 2002 by Wrox Press

Current Thread