LISTSERV mailing list manager LISTSERV 16.0

Help for XML-L Archives


XML-L Archives

XML-L Archives


XML-L@LISTSERV.HEANET.IE


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XML-L Home

XML-L Home

XML-L  April 2001

XML-L April 2001

Subject:

Re: Xalan Performance

From:

Paul Kelly <[log in to unmask]>

Reply-To:

General discussion of Extensible Markup Language <[log in to unmask]>

Date:

Thu, 19 Apr 2001 16:36:30 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

All my experience of Xalan is Windows-based, but I think the following
comments can be applied to Xalan on Linux as well.

First, the later Java run-time environments use a JIT (just in time)
compiler, so when you start executing Xalan, the run-time is compiling and
optimizing the code as it executes. Xalan also loads Xerces, so there are a
*lot* of classes being loaded, compiled and optimized.

Xalan is also loading and compiling your XSL file into its own internal
format.

If you use the supplied command line processor to run Xalan, you only run
against one XML and one XSL file at a time.

The way to improve performance is to write your own command line processor
in Java, using the Xalan API to load and compile the XSL stylesheet once,
and then transform a whole load of XML files one after the other. Or if you
are transforming XML files on demand, say for a Web server, then you want a
Java process which the web server starts once to load Xalan, load the
stylesheet, and then run individual transforms against XML files as
required.

If you adopt this approach you can expect a 10-fold or more performance
increase out of Xalan.

The core of any such Java code is only a few lines long:


        // Set up processor & stylesheet - this code only needs to be
executed once.
    XSLTProcessor xsltProc = XSLTProcessorFactory.getProcessor() ;
    // Set the output type parameter in the stylesheet.
    StylesheetRoot xslStylesheet =
            xsltProc.processStylesheet(new XSLTInputSource
("stylesheet.xsl")) ;

    // Xalan is now set up and "stylesheet.xsl" is loaded and compiled

    // Each time you want to transform an XML file:

    xslStylesheet.process(new XSLTInputSource(xmlIn),
                          new XSLTResultTarget(xmlOut));

    // where xmlIn and xmlOut are String objects with the names of the input

    // and output files.


DISCLAIMER! This is code I've been running against Xalan 1.0.0 - check the
documentation for your version to make sure that this is correct.


Paul Kelly
MERANT E-Solutions
+44 (0) 1635 565362
http://www.merant.com


 -----Original Message-----
From:   Janning Vygen [mailto:[log in to unmask]]
Sent:   Wednesday, April 18, 2001 9:34 AM
To:     [log in to unmask]
Subject:        Xalan Performance

Hi,

i am using xalan XSLT processor (xalan-j_2_0_1 java on linux OS).

It takes 10 seconds to do a very simple transformation (1:1) with a very
small XML File (4 KB). Only thing to do is to parse entities and include
about 30 files. all xslt is just a 1:1 copy.

It takes 10 seconds on a AMD Athlon 700 with 128 MB and just a few other
processes running.

Is this a good performance for a XSLT processor?

If the xml file grows in size, will it take longer or are the 10 seconds
just
an overhead for the startup process?

regards
janning

--
Planwerk 6 /websolutions
Herzogstra?e 86
40215 Dusseldorf

fon 0211-6015919
fax 0211-6015917
http://www.planwerk6.de

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2017
August 2016
June 2016
March 2016
January 2016
July 2014
April 2014
January 2014
July 2013
February 2013
September 2012
August 2012
October 2011
August 2011
June 2011
January 2011
November 2010
October 2010
July 2010
June 2010
March 2010
February 2010
January 2010
November 2009
September 2009
August 2009
July 2009
May 2009
March 2009
December 2008
October 2008
August 2008
May 2008
March 2008
February 2008
January 2008
December 2007
October 2007
August 2007
June 2007
March 2007
January 2007
December 2006
September 2006
July 2006
June 2006
April 2006
February 2006
January 2006
November 2005
September 2005
August 2005
July 2005
June 2005
May 2005
March 2005
January 2005
October 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
December 1997
November 1997
October 1997

ATOM RSS1 RSS2



LISTSERV.HEANET.IE

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager