use Perl

• check regexen (Score:2)

  by TeeJay (2309)

  We had a similar problem at foresite with some very complex regular expressions - some operations in the template parsing system (built out of 1 hugely complex regex and hundreds of smaller regexes and functions) became about 10 to 20 times slower. It was fixed by changing how the regexes worked to reduce the impact of some changes to regexes that made some elements slower. Hope that helps

  --
  
  @JAPH = qw(Hacker Perl Another Just);
  print reverse @JAPH;
  • Re:check regexen (Score:2)

    by grantm (164)

    Hmm, that is interesting. We did have another problem where some of our regexes failed under 5.8. Apparently it was due to a bug that also existed in 5.6 but seldom reared it's head due to differences in memory allocation or something.
    
    Thanks.
• An update (Score:2)

  by grantm (164)

  Just to put this one to sleep. We didn't find a general problem of Perl 5.8 being slower. The one case where we had objective timings to compare was the one in my original post, where the job runtime jumped from 4.5 hours to 9 hours.
  
  When I profiled this job, I found it was spending the vast bulk of its time in a general purpose data formatting routine. I recoded it to use a more specific formatting routine and the runtime dropped to just over an hour - with the bulk of the remaining time being spent wait