It is far more efficient to return a reference to a large string than to return the string itself. Here are my benchmarks: 
sub Str {
  my $Str = q{
    # Here follows about 100K of ASCII data
  };
  $Str;
}
timethese(10000, {
  Str => q{ my $R = Str() }
});
Benchmark: timing 10000 iterations of Str...
       Str: 29 wallclock secs (28.64 usr +  0.01 sys = 28.65 CPU)

[download]
sub Ref {
  my $Str = q{
    # Here follows the same 100K of ASCII data
  };
  \$Str;
}
timethese(10000, {
  Ref => q{ my $R = Ref() }
});
Benchmark: timing 10000 iterations of Ref...
       Ref:  9 wallclock secs (10.50 usr +  0.00 sys = 10.50 CPU)

[download]

In reply to Re: Is it computationally expensive to return a large string (50-100 kB) from a sub? by Russ
in thread Is it computationally expensive to return a large string (50-100 kB) from a sub? by cbraga

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.