Beside the programming issues: Modern OS and Hardware tries to guess what "might come next" so i also think the 2nd read is from cache also keep in mind that depending on the "clustersize" (i hope i got the right word cmiiw) of your filesystem there might also be already more read than just the very small portion of the file you might access (512 Byte is the minimum which is adressed by harddisk), maybe tuning your filesystem could also help.
Last but not least faster hardware could be an option: software raid is, surprisingly performance related not far behind (on modern systems) hardware-raid if you could spend the money, i/o is in most cases the bottleneck. I also wonder if one could hold some of the files (maybe the often accessed) in a ram-disk, but i got no experience if this is possible ...

hth MH

In reply to Re^2: Reading files too slow by matze77
in thread Reading files too slow by Anonymous Monk

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.