Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Performance problem for Xalan-J on intel-dual core

Performance problem for Xalan-J on intel-dual core

2006-11-18       - By Brian Minchau
Reply:     1     2     3     4     5     6  

Robert,
the bulk of these synchronization/performance fixes (mostly from Toadie)
will be in 2.7.1 to be release. The 2.7.1 release will be out Friday
November 24, 2006 if all goes well. A number of similar patches from Dave
Brosius were also applied, although the performance implications of his
patches were not so clear, they were there mostly to move up to the "new"
collection classes in JRE 1.2

Of course a whole lot of other fixes will be included since this is the
first release since Aug 8, 2005  for 2.7.0. The laundry list will be in the
release notes.

- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
Xalan PMC
mailto:minchau@(protected)



                                                                         
            "Robert Houben"                                              
            <Robert.Houben@(protected)                                            
            sionware.net>                                              To
                                      <xalan-dev@(protected)>,        
            11/17/2006 04:38          <xalan-j-users@(protected)>      
            PM                                                         cc
                                                                         
                                                                  Subject
                                      RE: Performance problem for Xalan-J
                                      on intel-dual core                  
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         




Thanks for the heads-up and thanks especially to Toadie! This is very
useful information to have, as we have quite a few users running
multiprocessor and dual core systems using Xalan.

Do you know what version of Xalan these changes will get into?

-----Original Message-----
From: Brian Minchau [mailto:minchau@(protected)]
Sent: Friday, November 17, 2006 1:27 PM
To: xalan-dev@(protected); xalan-j-users@(protected)
Subject: Performance problem for Xalan-J on intel-dual core


Over the last week I've been working with Toadie (a Xalan user) who had
some very serious performance degradation with a webserver using Xalan.

On an intel dual-core machine it was 10 times slowdown than for a single
processor intel machine.

The problem occurs in this combination for the latest code:
- Intel dual-processor
- Sun JRE 5


Toadie's team was very capable and found that there was thread
contention
with synchronized methods, either Xalan-J code or in JRE classes such as
java.util.Vector used by Xalan-J.  This performance problem was so bad
that
thread contention just screamed at us, and made it easy to fine the
"hot"
synchronization spots. With their direction I changed Vector to the
unsynchronized ArrayList in a number of locations got back most of the
performance for them.

Toadie previously let me know that a single processor did not have this
problem, and recently checked that the IBM JRE 5 does not have the same
synchronization performance problem on the dual-core machine.

So heads up on Xalan's next multiprocessor performance problem.

Hats off to Toadie who did a great job of analysis, providing hardware
to
do the analysis, and even the patches.


- Brian Minchau
mailto:minchau@(protected)