Thanks for the suggestion!
Between sawampersand and grep'ing my code, I did find an instance of $&. I removed it, but I am still seeing the problem.
Did you actually use Devel::SawAmpersand to test it? There are other modules that pull those in, e.g. if you do 'use English'.
I have also noticed that the size of our mod_perl processes has doubled since the upgrade (from ~50M to ~100M). Did Perl, Apache, and mod_perl really get that much bigger between the versions I mentioned in my last email?
Perl is getting bigger all the time but definitely not by this amount. Use Apache::Status coupled with all the goodies it invokes (B::Size etc) to figure out who eats your memory. If you have your perl built with ithreads (to check run: perl -V:useithreads), recompile it to not enable those (unless you plan to use them). You will find quite a few other performance/memory usage related tips in the "Practical mod_perl" book [1].
Also in your original report, the example of using Time::HiRes is highly unreliable. You need to count CPU clocks, not wallclocks. Use Benchmark.pm instead.
Also have you tried using some special purpose CPAN module to do the parsing for you? e.g. I remember Randal's WebTechniques articles [2] have plenty of examples of using modules like HTML::Filter, HTML::Tree, etc.
[1] http://modperlbook.org/ [2] http://www.stonehenge.com/merlyn/WebTechniques/
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
