Perrin Harkins wrote:
> Back to your idea: you're obviously interested in the low-level > optimization stuff, so of course you should go ahead with it. I don't > think it needs to be a separate project, but improvements to the > performance section of the guide are always a good idea. It has to be a run-able code, so people can verify the facts which may change with different OS/versions of Perl. e.g. Joe says that $r->args is slower then Apache::Request->param, I saw the opposite. Having these as a run-able bits, is much nicer. > I know that I > have taken all of the DBI performance tips to heart and found them very > useful. :) That's mostly JWB's work I think. > I'm more interested in writing about higher level performance issues > (efficient shared data, config tuning, caching), so I'll continue to > work on those things. I'm submitting a proposal for a talk on data > sharing techniques at this year's Perl Conference, so hopefully I can > contribute that to the guide after I finish it. Go Perrin! _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
