I made the changes you mentioned. I had missed visnu's %common, and your code and PMGurus code ignored the common words, in my version. Also, since the PMGurus code does lower-case the words in the grep, I have included those results.

Thanks for pointing out what I had missed.

Here is the latest code, and results: 

@common = qw|a an and at the to|;

timethese(1000, {
  Odud => q{
    my (@only, %r, %seen);

    foreach $r (@words){
      $r{lc $r} = 1;
    }
    my @uniqwords = sort keys %r;

    foreach my $item (@uniqwords) {
      push(@only,$item) unless exists $seen{$item};
    }
    my @newwords = @only;
  },
  PMGurus => q{
    my %seen;
    @seen{@common} = (1) x @common;
    my @newwords = sort grep !$seen{+lc}++, @words;
  },
  btrott_OneLiner => q{
    my %seen;
    @seen{@common} = (1) x @common;
    my @newwords = sort grep !$seen{$_=lc}++, @words;
  },
  btrott_FirstPass => q{
    my (%seen, %r);
    @seen{@common} = (1) x @common;
    for my $r (@words) {
      next if exists $seen{ lc $r };
      $r{lc $r} = 1;
    }
    my @newwords = sort keys %r;
  },
  visnu => q{
    my %common;
    @common{@common} = (1) x @common;
    my @newwords = sort keys %{+{ map { !$common{$_ = lc $_} ? ($_, 1)
+ : () }
                                       @words }};
  },
});

Benchmark: timing 1000 iterations of Odud, PMGurus, btrott_FirstPass, 
+btrott_OneLiner, visnu...
           Odud:  9 wallclock secs ( 9.61 usr +  0.00 sys =  9.61 CPU)
        PMGurus:  6 wallclock secs ( 5.40 usr +  0.00 sys =  5.40 CPU)
btrott_FirstPass: 7 wallclock secs ( 7.07 usr +  0.00 sys =  7.07 CPU)
btrott_OneLiner:  6 wallclock secs ( 5.73 usr +  0.00 sys =  5.73 CPU)
          visnu: 10 wallclock secs (10.29 usr +  0.00 sys = 10.29 CPU)

[download]
Russ
Brainbench 'Most Valuable Professional' for Perl

In reply to RE:(3) List processing (benchmark results) by Russ
in thread List processing performance by Odud

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.