RE: [xsl] Saxon for windows?

[Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>]

Hi George,

Your point is valid. In my performance test application it's more than
evident. But that's the same for .NET - if the .NET application runs for the
first time the same happens or worse. 

The application I developed shows those delays quite clear, and in the
performance tests I've done I was ignoring at least first or even second
time runs. 

It might well be an advantage to use precompiling for .NET in this case, but
still then I'd seriously look into performance in each and every deploy.

Cheers,
Pieter

-----Original Message-----
From: George Cristian Bina [mailto:george@xxxxxxx] 
Sent: Friday, June 03, 2005 10:52 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Saxon for windows?

Hi Pieter,

 > It's actually quite simple. I'm using a process class which allows me to
> capture StdOut and StdErr, and that runs a process in the background. The
> background process can be anything that runs via a command line, and the
> best is that it runs completely independent (in Windows this just means on
> another thread). While threads compete with each other for CPU time, when
> the process runs, the main thread just waits for its output, which means
> that the child thread can use all CPU available, thus maximum performance
is  > guaranteed (under normal circumstances and no other tasks running
assumed).

What about the java start up time? You will add that at each run.
And if you run the transformation only once then I think you will not get
the best of Java either - I always hear that if you want to measure how much
time a stylesheet takes for processing you should not look at the times of
the first runs.

My 2 cents...

Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com