in reply to Re^6: list of unique strings, also eliminating matching substrings
in thread list of unique strings, also eliminating matching substrings

That looks like you do not have Inline::C installed correctly, but I can't help you with that. If it is the case...ie. if the Inline::C installation tests are failing, then you shoudl post a new thread about that to get help.

In the interim, you can try this pure perl version which is only half as fast as the inline version, but that should still be 7 times faster than your current solution. Let me know how you get on.

#! perl -slw use strict; use Time::HiRes qw[ time ]; $|++; sub uniq{ my %x; @x{@_} = (); keys %x } my $start = time; my @uniq = uniq <>; chomp @uniq; @uniq = sort{ length $a <=> length $b } @uniq; my $all = join chr(0), @uniq; my $p = 0; for my $x ( @uniq ) { $p += 1+ length $x; next if 1+ index $all, $x, $p; ## COrrected per LanX below. print $x; } printf STDERR "Took %.3f\n", time() - $start;

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^7: list of unique strings, also eliminating matching substrings
  • Download Code

Replies are listed 'Best First'.
Re^8: list of unique strings, also eliminating matching substrings
by LanX (Saint) on Jun 02, 2011 at 15:05 UTC
    I had a similar idea but with some modifications:

    1. starting with the longest string and continuing in descending order

    2. then only appending the non-embeddable strings to $all

    like this $all is in average significantly shorter and the tests with index should be faster.

    I'm also wondering if the reallocation of new memory when appending to $all could be avoided by starting with a maximal length string and then shortening $all again.

    Maybe uniq() from List::MoreUtils is faster or could be completely avoided (after sorting identical strings always appear in a sequence)

    All of this highly depends on the nature of the unknown data and should only be tested with identical sets...

    Cheers Rolf

      1. 1. starting with the longest string and continuing in descending order

        I don't get the idea of putting the longest first?

        The idea of putting the shortest first is that you can use the third parameter to index to skip over the shorter strings as you've checked them. Longer strings can never be contained by the shorter ones, and starting the search part way into the string is much cheaper than trimming the shorter ones off the end.

      2. 2. then only appending the non-embeddable strings to $all

        I do not know what you mean by "non-embeddable" in this context?

      3. I'm also wondering if the reallocation of new memory when appending to $all could be avoided by starting with a maximal length string and then shortening $all again.

        If you mean counting the space required for $all, allocating to that final size and then copying the elements into the string--rather than building it up by appending each element in turn--that is exactly what join does.

      4. Maybe uniq() from List::MoreUtils is faster

        Not in my tests. Mine usually works out ~15% faster.

      5. or could be completely avoided (after sorting identical strings always appear in a sequence)

        That would mean sorting the duplicates. Sorting is O(N log N); de-duping O(1). And after the sorting, you;d still need to make a complete pass with grep to remove the dups before joining.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
        hmm ... actually I didn't want to invest time coding for this xy-nonsense.

        But maybe it's easier to show code instead of explaining the theory

        (UPDATE-06-03 13:37 GMT: fixed bug in initialization and missing uniqifying)

        --- Init ... ... completed: 2000 snippets from 200 to 400 of 6000 long DNA Check_all took 1.206 Filtered: 287 Ratio: 6.96864111498258 Check_longest took 0.436 Filtered: 287 Ratio: 6.96864111498258 Faster: 2.76641019482413 --- Init ... ... completed: 2000 snippets from 200 to 400 of 60000 long DNA Check_all took 2.990 Filtered: 924 Ratio: 2.16450216450216 Check_longest took 1.908 Filtered: 924 Ratio: 2.16450216450216 Faster: 1.56725918185693 --- Init ... ... completed: 2000 snippets from 200 to 400 of 600000 long DNA Check_all took 4.462 Filtered: 1785 Ratio: 1.12044817927171 Check_longest took 4.058 Filtered: 1785 Ratio: 1.1204481792717 +1 Faster: 1.09963952407683 --- Init ... ... completed: 2000 snippets from 200 to 400 of 6000000 long DNA Check_all took 4.601 Filtered: 1977 Ratio: 1.01163378856854 Check_longest took 4.651 Filtered: 1977 Ratio: 1.0116337885685 +4 Faster: 0.989378646160973

        Cheers Rolf

Re^8: list of unique strings, also eliminating matching substrings
by LanX (Saint) on Jun 02, 2011 at 16:02 UTC
    just noticed that index returns -1 for a missing match.

    you say this worked?

        next if index $all, $x, $p;

    did you manipulate $[ somewhere???

    Cheers Rolf

      You're right. I edited rather than c&p :( and forgot my usual 1+.

      next if 1+index $all, $x, $p;

      Code above amended.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.