And you don't mention the OS or how your files are laid out, but be aware that on many *NIX variants some filesystems have problems with large (FSVO large that varies by filesystem) numbers of files in a single directory. For (say) an ext2 fs 10,000 would count and you'd notice a good bit of latency for any operation on the containing directory.

A common workaround is to break the files up into subdirectories keyed by part of the filename or something derived from the filename (e.g. if the filenames were 5 digit numbers have 10 top level directories 0..9 each of which has its own subdirectories 0..9 and the file 12345.foo would be located in 1/2/12345.dat).

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re: Reading files too slow by Fletch
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.