Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

Re: see XML::LibXML::Reader

by mirod (Canon)
on Dec 07, 2008 at 10:50 UTC ( [id://728688]=note: print w/replies, xml ) Need Help??


in reply to see XML::LibXML::Reader
in thread processing massive XML files with XML::Twig

Interesting. I have to see if I can see this as an alternate parser for XML::Twig. Or to create a different module alltogether, that combnes the speed of libxml2 with the convenience (IMHO ;--) of XML::Twig.

It would be great if you (or someone else!) could provide code examples for the Ways to Rome" series.

Replies are listed 'Best First'.
Re^2: see XML::LibXML::Reader
by Anonymous Monk on Dec 07, 2008 at 21:52 UTC
    Your benchmarking methodology is much less accurate than it could be. You shouldn't be measuring the time it takes to fork a new process and load the modules, and should be measuring multiple runs and averaging the results- ex. timethese(-5, ...).

      I happen to think that load time is important, and the time to fork should impact all tests similarly.BTW XML::Twig does probably very badly in this respect, so you can't say I am biased.

      As far as I know, no one has ever challenged the "SAX is lightweight and fast" before I published this benchmark. And no one since then has ever come up with any figure that would prove me wrong when I say "SAX is slow".

      Of course my benchmarks are imperfect. Of course I am sure you could do better. Then do it.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://728688]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others exploiting the Monastery: (7)
As of 2024-04-19 12:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found