I may sound like broken record for saying this since it is common advice, but it's good advice so I just have to ask. What is your specific performance issue with the if statement in question, and what profiler data do you have to back up that assertion?

Many optimization problems over which people agonize, plan, and scheme aren't really problems at all. If serialization is important, I can't imagine what performance degradation a simple conditional is causing that would be worth a bunch of extra code to do the serialization. I could see that degradation in a hot spot of the code, though, if a profiler actually showed it.

In reply to Re: Creating a Moose object and serializing it by mr_mischief
in thread Creating a Moose object and serializing it by daverave

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.