I don't think so, I mean in the first place I got rid of this interpolation problem by testing the log level using a call to Log4perl: 

if ($self->{logger}->is_trace()) { # for efficiency (not to compute th
+e expression) 
            $self->{logger}->trace("total NbObsThis $i=$nbObservedThis
+NGram->[$i]; nbObsAll $i=$nbObservedAllNGrams->[$i]; total=$totalObse
+rvedAll; nbExpected $i=$nbExpectedThis[$i]; chisq = $chiSquare[$i]")
}

[download]

It helped indeed, but the cost of "is_trace()" was still prohibitive. Then I added a new variable $self->{disableLogger} set to true if the level is OFF (testing the log level only once) and replaced the condition with 

if (!$self->{disableLogger} && $self->{logger}->is_trace()) { # test f
+or efficiency (not to compute the expression) {
            $self->{logger}->trace("total NbObsThis $i=$nbObservedThis
+NGram->[$i]; nbObsAll $i=$nbObservedAllNGrams->[$i]; total=$totalObse
+rvedAll; nbExpected $i=$nbExpectedThis[$i]; chisq = $chiSquare[$i]")
}

[download]

and this takes way less time (according to NYTProf). As previously said, it seems that a simple call to is_debug() (no interpolation) implies a complex (and long) computation in Log4perl.

In reply to Re^3: log4perl and efficiency by erwan
in thread log4perl and efficiency by erwan

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.