Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Enhancing parsing performance

Enhancing parsing performance

2003-01-13       - By Brian Madigan
Reply:     1     2     3     4     5     6     7     8     9     10  

You could try not creating a new parser all the time,
although this might cause other problems. Im guessing
that this code is only that slow THE FIRST TIME
THROUGH. Hopefully after the JVM hotspots it, this
block of code runs much faster. You are not doing any
validation apparently, so you cant gain any more
performance by turning that off. I cant imagine that
parsing a 3k file is taking 4 seconds. If you want an
accurate measure, try taking snapshots of the system
time (System.currentTimeMillis( )) before and after
parse( ) method call. The 4 seconds you describe could
be the JVM loading and object initialization. Also, I
don't recommend going around factories to instantiate
concrete classes. Unless the factories are really
heavy you won't see a substiantial performance gain.

long start = System.currentTimeMillis( );
parser.parse(m_file.toURI().toString());
m_document = parser.getDocument();
long end = System.currentTimeMillis( );
System.out.println("parse time: "+(end-start)+" ms");

--- Jean Georges PERRIN <jgp@(protected)> wrote:
> Hi,
>
> Thanks for those who helped me with cloning...
>
> I am a little surprised with performance. Maybe
> there are some basic things
> I am doing wrong.
>
> I am parsing a 3 Kb XHTML file and it takes me about
> 4s, cloning the tree
> takes me roughly a ridiculous amount of time (10ms).
> This on an Athlon XP
> 1800+ running XP (sure I could switch to Linux but
> it is not planned for now
> :) ).
>
> My code for parsing:
>   protected void load () {
>     DOMParser parser;
>    
>     try {
>       parser = new DOMParser();
>     }
>     catch (Exception e) {
>       log.severe ("Error: Unable to instantiate
> parser");
>       return;
>     }
>
>     try {
>       parser.parse(m_file.toURI().toString());
>       m_document = parser.getDocument();
>     }
>     catch (SAXParseException e) {
>       // ignore
>     }
>     catch (Exception e) {
>       String msg;
>       msg = ("Error: Parse error occurred, " +
> e.getMessage());
>       if (e instanceof SAXException) {
>         e = ((SAXException)e).getException();
>       }
>       msg += '\n' + e.toString();
>       log.severe (msg);
>     }
>   }
>
> Questions:
> 1/ is static'ing my parser will enhance the process?
> 2/ can I "pre" create some objects I can reuse?
> 3/ are there some eventual verification I can turn
> off?
>
> My code for cloning:
>   public Object clone() {    
>     XHTML11Window win = new XHTML11Window(m_file);
>     win.m_document = new DocumentImpl();
>    
>
win.m_document.importNode(m_document.getDocumentElement(),
> true);
>    
>     return win;
>   }
>
> I haven't checked that they really were cloned, but
> it looks as if they
> were...
>
> Any tips are more than welcome!
>
> Jean Georges PERRIN
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> xerces-j-user-unsubscribe@(protected)
> For additional commands, e-mail:
> xerces-j-user-help@(protected)
>


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)