stas        2002/07/29 23:04:15

  Modified:    src/docs/1.0/guide performance.pod
  Log:
  add a resource describing how to write a more efficient code
  Submitted by: Rob Nagler
  
  Revision  Changes    Path
  1.20      +34 -0     modperl-docs/src/docs/1.0/guide/performance.pod
  
  Index: performance.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/performance.pod,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- performance.pod   14 Jul 2002 06:48:08 -0000      1.19
  +++ performance.pod   30 Jul 2002 06:04:15 -0000      1.20
  @@ -3594,6 +3594,17 @@
   
   in the normal way (no C<E<lt>PerlE<gt>> section required).
   
  +
  +
  +
  +
  +
  +
  +
  +
  +
  +
  +
   =head1 TMTOWTDI: Convenience and Habit vs. Performance
   
   TMTOWTDI (sometimes pronounced I<"tim toady">), or I<"There's More
  @@ -3612,6 +3623,11 @@
   benchmarks to support the theory, since however good the theory its
   the numbers we get in practice that matter.
   
  +"Premature optimizations are evil", the saying goes. I believe that
  +knowing how to write an efficient code in first place, where it
  +doesn't make the quality and clarity suffer saves time in the long
  +run. That's what this section is mostly about.
  +
   In the following benchmarks, unless told different the following
   Apache configuration has been used:
   
  @@ -4665,6 +4681,24 @@
     print "$filename was modified $mod_time seconds before startup\n";
   
   Two stat() calls were saved!
  +
  +=head2 Optimizing Code
  +
  +Here are some other resources that explain how to optimize your code,
  +which are usually applied when you profile your code and need to
  +optimize it but in many cases are useful to know when you develop the
  +code.
  +
  +=over
  +
  +=item *
  +
  +Interesting C code optimization notes, most applying to Perl code as
  +well: http://www.utsc.utoronto.ca/~harper/cscb09/lecture11.html#code
  +
  +=back
  +
  +[ReaderMETA]: please send me similar resources if you know of such.
   
   =head1 Apache::Registry and Derivatives Specific Notes
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to