XML::Twig uses XML::Parser (Expat) to parse XML, but XML::Parser is just not that fast of a parser.*

SOAP::Lite uses XML::Parser as well. I wrote a patch that makes SOAP::Lite use XML::LibXML. Including the time it takes to convert XML::LibXML's output to XML::Parser's format, XML::LibXML was 12x faster. 

         Rate  Expat LibXML
Expat  9.09/s     --   -92%
LibXML  118/s  1202%     --

[download]

Now, XML::LibXML is not a good solution for XML::Twig since XML::Twig is designed to work with huge documents and streams, but maybe XML::Twig is not the best solution for you.

* — It blows off the pants off every alternative I tried as the backend for XML::Simple, so it's not exactly a slouch either.

In reply to Re: Perl_XML Twig Performance query by ikegami
in thread Perl_XML Twig Performance query by niranjan_ng

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.