Can you please tell us what you mean exactly by
slow? Or, in other words, how many bytes (or megabytes, whatever) you're processing per unit of time? And, if possible, how much faster your would expect tor want) it to be?
For finding the slow parts in your program, the best is probably to use a profiling tool such as Devel::NYTProf.
Otherwise, as a general comment, I would suspect that using the regex engine in a loop to fetch one byte at a time is probably quite inefficient. unpack is very likely to be significantly faster if you can use it. Even substr in a loop is quite probably going to run faster.
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.