Re: AW: some XSLT benchmarks

2002-02-21 Thread scott_boag
EMAIL PROTECTED], (bcc: Scott Boag/Cambridge/IBM) Subject: Re: AW: some XSLT benchmarks

Re: AW: some XSLT benchmarks

2002-02-20 Thread Stefano Mazzocchi
[EMAIL PROTECTED] wrote: > > Yes, I agree with Berin on this, though I also agree with Jacek that > there's little reason that it should not scale well. > > Another factor is "incremental" output, which Xalan interpretive does a lot > of work to do well (and tends to take penalty for), and XSLTC

Re: AW: some XSLT benchmarks

2002-02-20 Thread Berin Loritsch
Santiago Pericas wrote: >> yes, automatically generated, but the 'XSLT to bytecode' patterns have >> been manually crafted, right? and I'm pretty sure that you guys crafted >> them based on the assumption on how the underlying JVM was going to >> interpret them. Which shows why it is faster on the

Re: AW: some XSLT benchmarks

2002-02-20 Thread Santiago Pericas
> yes, automatically generated, but the 'XSLT to bytecode' patterns have > been manually crafted, right? and I'm pretty sure that you guys crafted > them based on the assumption on how the underlying JVM was going to > interpret them. Which shows why it is faster on the Sun 1.3.1 JVM (but > this i

Re: AW: some XSLT benchmarks

2002-02-20 Thread scott_boag
[EMAIL PROTECTED], Santiago Pericas <[EMAIL PROTECTED]> 02/19/2002 11:22 Subject: Re: AW: some XSLT benchmarks

Re: AW: some XSLT benchmarks

2002-02-20 Thread Jacek Ambroziak
You guys may find another data point interesting... (I am using Sun's newest 1.4 on Linux) I reran the test with '-verbosegc' flag gathering GC info into files. and then counted Full garbage collections grep Full gcXSLTC | wc -l grep Full gcXT| wc -l and so on. The results: XSLTC21 X

Re: AW: some XSLT benchmarks

2002-02-20 Thread Stefano Mazzocchi
Santiago Pericas wrote: > > > yes, automatically generated, but the 'XSLT to bytecode' patterns have > > been manually crafted, right? and I'm pretty sure that you guys crafted > > them based on the assumption on how the underlying JVM was going to > > interpret them. Which shows why it is faster

Fwd: Re: AW: some XSLT benchmarks

2002-02-20 Thread Jacek Ambroziak
Note: forwarded message attached. __ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com --- Begin Message --- No assumptions about JVMs have been made; in fact translets used to run faster on IBM's VMs (esp.

Re: AW: some XSLT benchmarks

2002-02-20 Thread Jacek Ambroziak
No assumptions about JVMs have been made; in fact translets used to run faster on IBM's VMs (esp. 1.1.8) which was a bit embarassing for me as a Sun-er at the time. I am sure translets can be further optimized but JVM tuning would be the last (if at all) place to look at, maybe except for small d

Re: AW: some XSLT benchmarks

2002-02-20 Thread Stefano Mazzocchi
MORAVEK Peter wrote: > > > Results: > > Xalan 2.3 XSLTC > > XT > > MSXML 3.0 > > And what about SAXON and MSXML 4.0 ? How are the results of the benchmarks > with these two transformers ? Saxon was way slower (around 100, check my previous post on the matter) I couldn't test MSXML 4.0 because

Re: AW: some XSLT benchmarks

2002-02-20 Thread Stefano Mazzocchi
Jacek Ambroziak wrote: > > Stefano, > > that is cool! Except for the mysterious 'dbonerow'. I > will attempt to fix it > an in general I am going continue to follow my > original vision > to make XSLTC a good technology for people to actually > use. Cool. > You are right, there are multiple '

RE: AW: some XSLT benchmarks

2002-02-19 Thread MORAVEK Peter
> Results: > Xalan 2.3 XSLTC > XT > MSXML 3.0 And what about SAXON and MSXML 4.0 ? How are the results of the benchmarks with these two transformers ? Thanks Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional co

Re: AW: some XSLT benchmarks

2002-02-19 Thread Berin Loritsch
Jacek Ambroziak wrote: > --- Berin Loritsch <[EMAIL PROTECTED]> wrote: > >>Stefano Mazzocchi wrote: >> >>>"Jacek R. Ambroziak" wrote: >>> >>> > >>>Anyway, seriously, XSLTC *is* a solution to the >>> >>XSLT bottleneck problem. >> > >>My question is this: how does it _scale_. >> >> > >>I would

Re: AW: some XSLT benchmarks

2002-02-19 Thread Jacek Ambroziak
--- Berin Loritsch <[EMAIL PROTECTED]> wrote: > Stefano Mazzocchi wrote: > > "Jacek R. Ambroziak" wrote: > > > > Anyway, seriously, XSLTC *is* a solution to the > XSLT bottleneck problem. > > > My question is this: how does it _scale_. > > I would like to see the *same* tests with 100 > th

Re: AW: some XSLT benchmarks

2002-02-19 Thread Jacek Ambroziak
Stefano, that is cool! Except for the mysterious 'dbonerow'. I will attempt to fix it an in general I am going continue to follow my original vision to make XSLTC a good technology for people to actually use. You are right, there are multiple 'goto's' in the generated bytecodes (although the by

Re: AW: some XSLT benchmarks

2002-02-19 Thread Berin Loritsch
Stefano Mazzocchi wrote: > "Jacek R. Ambroziak" wrote: > > Ideal should for the XSLTC engine to recognize the JVM it runs in (via > system properties) and tune the generated bytecode on the running JVM. I > assume this could give some 20/30% more speed improvement, but it's a > potentially harmfu

Re: AW: some XSLT benchmarks

2002-02-19 Thread Stefano Mazzocchi
"Jacek R. Ambroziak" wrote: > > Stefano, > > A new xmdrivers.jar is attached with an updated drived for XSLTC. > You can now run your tests again. Ok, ran the tests on my laptop, same hardware/software/condition as before. Results: Xalan 2.3 XSLTC --- Sun 1.3.1 [1]118

Re: some XSLT benchmarks

2002-02-19 Thread Torsten Curdt
On Mon, 18 Feb 2002, Jacek R. Ambroziak wrote: > Took me a while to recreate XSLTC driver for XSLTMark > but it appears to be working now. Here are the results: > > Dell Inspiron 8000 > Intel Pentium III (Coppermine) 900 MHz > 256 MB RAM > Red Hat Linux 7.1, kernel 2.4.16 > > "magic numbers" (w/

Re: some XSLT benchmarks

2002-02-18 Thread Jacek R. Ambroziak
Took me a while to recreate XSLTC driver for XSLTMark but it appears to be working now. Here are the results: Dell Inspiron 8000 Intel Pentium III (Coppermine) 900 MHz 256 MB RAM Red Hat Linux 7.1, kernel 2.4.16 "magic numbers" (w/ test 'dbonerow' disabled) XSLTC493 XT 377 Saxon

Re: AW: some XSLT benchmarks

2002-02-18 Thread Davanum Srinivas
Scott, FYI, Right now the Translets are unusable for C2 :( http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6312 Thanks, dims --- [EMAIL PROTECTED] wrote: > > 5) i haven't tested Xalan Translets, which, along with compiled XML > > might be *the* way to go for Cocoon production environments >

Re: AW: some XSLT benchmarks

2002-02-18 Thread Jacek R. Ambroziak
If you would like to discuss the technical > details of what's going on, I would be glad to. The issues aren't simple, > though the results and the perception of the results are. > > -scott > > > > > > Jörn Heid >

Re: AW: some XSLT benchmarks

2002-02-18 Thread scott_boag
in [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 17. Februar 2002 23:21 An: 'Stefano Mazzocchi '; 'Apache Cocoon ' Cc: 'Apache Xalan ' Betreff: RE: some XSLT benchmarks Thесе benchmarkс make it clear that Xalan J is far from the winner. For completeness however, wouldn'

AW: some XSLT benchmarks

2002-02-17 Thread Jörn Heid
27;Stefano Mazzocchi '; 'Apache Cocoon ' Cc: 'Apache Xalan ' Betreff: RE: some XSLT benchmarks Thесе benchmarkс make it clear that Xalan J is far from the winner. For completeness however, wouldn't it be fare to include XSLTC as well. Also Electric XML is a fast free pa

RE: some XSLT benchmarks

2002-02-17 Thread Ivanov, Ivelin
gards, Ivelin -Original Message- From: Stefano Mazzocchi To: Apache Cocoon Cc: Apache Xalan Sent: 16.2.2002 a. 10:58 Subject: some XSLT benchmarks [crossposting on xalan-dev since they might be interested in these results] I want to have numbers to know whether or not a native implement

some XSLT benchmarks

2002-02-16 Thread Stefano Mazzocchi
[crossposting on xalan-dev since they might be interested in these results] I want to have numbers to know whether or not a native implementation of an XSLT transformer for Cocoon would make sense, so I did some benchmarks. I used XSLTMark and rerun the test on my machine (old laptop, but anyway