Quick answers

1. A disk access is about 1000 times slower than memory access and thus the hash is much faster, unless the hash is too big to fit the main memory.

2. On unix, and most likely on Windows too, disk access gets cached (due to the above reason) and thus the chdir won't make much difference since find() needs to access the directory once and thus it is in the cache.



Using your hash will most likely speed things up, Note that the hash can contain only the roots in @INC and thus is very short. For this, just sort @INC and thus you will have the prefixes before the rest.

In reply to Re: Wondering about File::Find by fundflow
in thread Wondering about File::Find by jynx

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.