I am willing to bet your grep is the slowest bit, but have you profiled the code? Anyhow, assuming the grep bit is your bottleneck:
## your original code
@{$sets{$fasta_id}[$setscounter]{$sitekey}} = grep {
$_ >= $lowerlimit and $_ <= $upperlimit
} @{$matches{$fasta_id}{$sitekey}};
Depending on your data, you may gain some performance by using a sorted array instead:
@{$sets{$fasta_id}[$setscounter]{$sitekey}} = ();
foreach ( sort @{$matches{$fasta_id}{$sitekey}} ) {
last if $_ > $upperlimit;
next if $_ < $lowerlimit;
push @{$sets{$fasta_id}[$setscounter]{$sitekey}}, $_;
}
This will only have an advantage if sort is sufficiently fast and there are many elements above $upperlimit, so this suggestion comes with an extreme case of "know thy data".
<–radiant.matrix–>
Ramblings and references
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.