comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks