Have you specifically identified this as a problem for your application? I'm curious about this behavior if you have, including the technical details of the disks you are using. Can you elaborate?
If the amount of time that it takes you to get something off a disk is very large compared to whatever you are doing, something seems odd.
If that is really a problem though, you might want to look into a design that knows to buffer lines from the file, and to get more lines when it runs low. You're still paying the penalty for reading lines though. Something like sysread might give you a little boost, but then you have to spend time figuring out whre the line breaks are.
--
brian d foy <bdfoy@cpan.org>
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.