You are going about that completely the wrong way.

In breif, when you are testing the lines seperately, the chances are that the second line does almost nothing after having been repeated one or two times as there is nowhere left to lookdown() to.

However, when you repeat the two lines together, you are re-parsing the file each time, and so the tree is reset and lookdown() starts at the top and has some work to do every iteration.

Basically, you cannot profile code that has state by repeating it over and over without reseting the state each time.

The answer is to use the right tool for the job. Ie. Profiling and not Benchmarking. Get yourself over to CPAN and grab Devel::Smallprof. It's 10 times easier and a thousand times more accurate than the method your trying right now.

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller

In reply to Re: XML::TreeBuilder strange benchmarking behaviour by BrowserUk
in thread XML::TreeBuilder strange benchmarking behaviour by Mandor

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.