You're in luck! There are all sorts of methods to benchmark code. I found that there are some excellent explanations on benchmarking in the mod_perl guide.

While the mod_perl guide does talk about mod_perl, much of the information there is relevant to all Perl uses. The first example of benchmarking they give uses the Benchmark module, which you already tried. However, they give other examples using modules like Time::HiRes and GTop. Here is an example of the code you would use with Time::HiRes (copied from the mod_perl guide):

  use Time::HiRes qw(gettimeofday tv_interval);
 
  my $start_time = [ gettimeofday ];
  sub_that_takes_a_teeny_bit_of_time();
  my $end_time = [ gettimeofday ];
  my $elapsed = tv_interval($start_time,$end_time);
  
  print "The sub took $elapsed seconds."
[download]

But the good, juicy information doesn't stop there. They get into code profiling, memory usage, and other goodies -- including the speed differences between method calls vs function calls, along with offering various advice on good coding habits to reduce memory usage.

Feel free to skip any sections that are mod_perl/web specific, if that isn't what you intend to do. Again though, much of what they offer there goes for any code, not just mod_perl and web applications.
-Eric

---

---

• 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.