This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Updated Benchmark Available



----- Original Message ----- 
From: Alexey Gokhberg <alexei@bluewin.ch>


> The benchmark results look interesting, but what do they really
> demonstrate?

I think nothing.

> At my opinion, with the longest test running not more than 0.6 seconds,
> these results compare the time which XSLT engines need to warm-up and to
> cleanup, rather than the time they need to perform their main job.
> Furthermore, the warm-up and the cleanup time depends on the run-time
> system of the underlying platform (JVM, C++ RTL etc.), not on the
> quality of the XSLT processor itself.

Exactly.
 
> From the practical point of view, the result of this benchmark could be
> formulated as follows:
> 
> "... All XSLT processors (except those crashed) demonstrated a good
> performance ..." (0.6 sec is a good response time - isn't it?)

If your transformation consists of 5 sub-transformations  ( page
consists of 5 'sub-pages' )  the total responce time for  the 
page is 3 sec. This is not a good responce time, I think.
 
> I also could not understand why the issue whether the XSLT processor is
> using the "pre-parsed" stylesheets is so important. Some processors do
> it, some don't, but the efficiency of this feature in fact depends on
> the processor architecture and on the way how this pre-parsing is
> integrated with the other processor components.

I agree that pre-parsed stylesheets could be not critical for some 
environments, but I think it is actually easier to implement 
some brutal pre-parsed stylesheets instead of  argue about them.

In simple case pre-parsed stylesheets are saving the time of 
compilation .XSL into internal representation of the stylesheet
and no matter what is the XSLT engine architecture this 
compilation could be easeily avoided.  Or you see some 
other scenario when XSLT engine does not go from .XML 
to internal representation? 

Pre-parsing is important. Sometimes.

Rgds.Paul.




 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]