Paul Mineiro wrote:
right. i probably should've mentioned earlier that CGAT x 5 is
really fast in both mod_perl and command line.
if anybody wants my actual $seq data, please let me know.
i neglected to mention something big: the production version is
identical but using perl
Rob Mueller (fastmail) wrote:
I recently had a similar problem. A regex that worked fine in sample code
was a dog in the web-server code. It only happened with really long strings.
I tracked down the problem to this from the 'perlre' manpage.
WARNING: Once Perl sees that you need one of
Perrin Harkins wrote:
Your system has to be swapping horribly. I bet that the ulimit for
whoever apache is running as has the memory segment set super low.
apache is running as me on my unloaded desktop (no way this is going to
production until i figure this out). my ulimit -v is unlimited.
Robert Landrum wrote:
I just ran this on my system here... It's completely unloaded (load
average: 0.11, 0.08, 0.02)
Result:
0 wallclock secs ( 0.06 usr + 0.00 sys = 0.06 CPU) @ 16.67/s (n=1)
I ran it on a file that I created with
perl -e print 'ABCGEFSK' x 25000 /tmp/seqdata
Paul Mineiro wrote:
i've cleaned up the example to tighten the case:
the mod perl code snippet is:
---
my @cg;
open DIL, '', /tmp/seqdata;
print DIL $seq;
close DIL;
warn length seq = @{[length ($seq)]};
my $t = timeit (1, sub {
while ($seq =~ /CG/g
hi. i'm running mod_perl 1.26 + apache 1.3.14 + perl 5.6.1
i have a loop in a mod_perl handler like so:
my $stime = time ();
while ($seq =~ /CG/og)
{
push @cg, pos ($seq);
}
my $etime = time ();
warn time was: , scalar localtime ($stime), ,
scalar
