RE: [xsl] Latest XSLTMark benchmark

Subject: RE: [xsl] Latest XSLTMark benchmark
From: "Eugene Kuznetsov" <eugene@xxxxxxxxxxxxx>
Date: Wed, 4 Apr 2001 18:20:35 -0400
> You did not cover 4XSLT then, nor did any one of you contact the
> 4Suite list to ask about realistic test driver methodology.

The previous point was about Xalan, in response to David Bertoni's
concerns. It is true that the 4XSLT driver is a new addition in
this release, perhaps we should have put it in quarantine. Of
course, we have also had some folks contact us since the
article complaining that particular processors were "excluded" --
so perhaps including 4XSLT should be viewed as a good thing.

While I wasn't closely involved, I believe the driver is a
modified example from the 4XSLT distribution.

More to the point, in the case of 4XSLT we *did* ask for help
and, as a matter of fact, in the process one of our engineers
located three bugs in 4XSLT for which you yourself thanked him!

"You're not wasting our time.  After the confusion with your Python
upgrade, you actually ran across 3 legitimate bugs, one of which was
newly discovered (and now fixed in CVS)." [Uche Ogbuji in response
to "niko@xxxxxxxxxxxxx"]

I am not sure that XSLTMark itself was mentioned -- but presumably
the advice is the same for normal operation and for benchmarking!
If there is something we are doing wrong, please let us know. As
Michael Kay pointed out a few weeks ago on this very list, it is
not surprising that "one tends to do best in one's own benchmarks".

for the full exchange of messages between a DataPower engineer and
4XSLT folks).

> ### You've got to have all your stuff set up in a magic
> ### way for this to work.
> Was your intent to post dubious results so that you can get me to
> do all your work for you?

I am not sure that debating the contents of our source code
comments is particularly relevant to xsl-list, but perhaps you and
I can discuss this off-list.

> Your lack of documentation of method, constraints, restrictions,
> architecture, environment, etc. is *highly* unprofessional.

Actually, it is documented. And all the source code is open and
available so anyone can:

1. review it for proper behavior
2. independently reproduce the results
3. use it for internal testing (nice of us, no?)

Now, documentation aside, is there actually something wrong with
the driver? If you have specific problems with the 4XSLT driver,
please let us know (at xsltmark@xxxxxxxxxxxxx), and we will set
it right.

\\ Eugene Kuznetsov
\\ eugene@xxxxxxxxxxxxx
\\ DataPower Technology, Inc.

 XSL-List info and archive:

Current Thread