comment on

would something with a for loop and substr be faster? I dont necessarily have to unpack any bytes, do I?

That requires a call into C (substr) for every byte; where using unpack requires a single call for the entire string.

The cardinal rule for optimising Perl code, is to get perl's built-ins to do as much of the work as you can.

Using this loop:

    ++$seen[ ord chop $buf ] while length $buf;
[download]

in place of the unpack loop is almost but not quite as fast.

It trades 2 built-in calls per byte, against the cost of building the unpack return list on the stack, and loses by a hair.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

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". I knew I was on the right track :)

In the absence of evidence, opinion is indistinguishable from prejudice.

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.