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 Issue

Performance Issue

2007-04-09       - By alapati.sasi
Reply:     1     2     3  


Hi Henry,
Good Morning .
i have done a little programming on this .

i have a source xml without any namespace bindings and prefixes. i have a
xsl stylesheet to transform this source xml .

i am directly transforming it . for 10000 requests its taking some 548 sec's
to transform all the 10000 .

Now i modified the same source xml . Now the source xml contains namespace
bindings . Now my stylesheet will not work .
So i changed my java code so that it will take the source xml first and then
apply the stylesheet which whill remove namespace bindings from source xml
.Now this removed all the namespace bindings & prefixes.Now i applied my
original stylesheet. for 10000 requests its taking nearly 553 sec's now .

but what i thought was it will take more time in the second approach than in
first bcoz we are doing one more additional step here for removal of
namespace. But the results are not like that .

i dont know why both have taken same time . can you please tell me the
reason if you know ? Any way i am using xalan to transform the xml.

Now i am in a confusion why the second one with one more step more have
taken same time as of first ??????
Any Idea on how xalan internal performance .
The solution is fine but i need to explain the solution to managers then
immediate question will be what abt performance and why performance is same
if you are using one more extra transformation for each request . Any Xalan
developer if you know the answer let me know yaar .
Thanks Henry for you valuable reply.

Thanks & Regards
Sasi.A

Henry Zongaro wrote:
>
> Hello.
>
> "alapati.sasi" <alapati.sasi@(protected)> wrote on 2007-04-04 02:47:28 PM:
>> i need to transform a big source xml into target xml . My source xml
> comes
>> with the namespace prefix and my xsl doesnt contain any prefixes for
> xpath.
>>
>> its very difficult to change all the xpath's at run time for me .
>>
>> i have two options
>> 1) First change the source xml to another xml file using
>
> [HZ:  Removed stylesheet to create copy using just local names, no
> namespaces]
>
>> this template .This will remove all the prefix bindings .
>> Now apply my original style sheet .I Will get the target xml.
>> Is this cause me performace hit ?
>> Is it better to do like this or Is it better to have local-name() in the
>> stylesheet itself so that there is no additinal transformation required
> .
>> But if i use local-name() for all the xpath's i heard that processing
> time
>> will take more time ?
>
> You're right that using a path expression like "*[local-name()='foo']"
> will not perform as well as using the expression "foo" or "p:foo".  My
> instinctive reaction is that your other alternative of using a
> preprocessing stylesheet that strips out namespaces will probably perform
> worse.  If the input to a stylesheet is very large, the time spent
> constructing the input data model and serializing the result (assuming
> that that is about as large) often dominates the performance; in this
> case, you would be doing all of that twice.  However, it really depends on
> your particular XML and XSL.  Your best bet would probably be to prototype
> both solutions, and see how they perform for your particular.
>
> If you're using the SAX API to deliver your XML to your stylesheet,
> another option might be to apply some filtering of the SAX events that
> removes namespace declarations, and changes element and attribute names to
> equivalent, non-namespaced names.
>
> I hope that helps you with your decision.
>
> Thanks,
>
> Henry
> ------------------------------------------------------------------
> Henry Zongaro      XSLT Processors Development
> IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
> mailto:zongaro@(protected)
>
>

--
View this message in context: http://www.nabble.com/Performance-Issue-tf3527549
.html#a9904384
Sent from the Xalan - J - Users mailing list archive at Nabble.com.