It would be unusual for a small read size to boost performance, at least with spinning rust. Even if it were the case, changing Perl's minimum read size will almost certainly not make any difference to how the OS buffers file I/O so it's likely that you can only hurt performance by increasing the number of calls into the OS to get work done.
Maybe there is some other reason you are getting a performance hit (assuming this isn't just "I wonder what would happen ..." territory). If you have a real performance problem to solve, perhaps you would like to tell us more about it so we may be able to offer some more substantial advice?
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
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.