The advantage of chdir(), at least on some systems, is that the whole path doesn't need to be traversed for each directory and file access. If you don't chdir(), then you are doing things like stat("sub/dir/tiny/file") which, even if the cache works very effectively, has to find "sub", then find "dir", then find "tiny", then find "file".

If you chdir(), then your process keeps a handle into that directory so that stat("file") doesn't have to even look in the cache for "sub", "dir", and "tiny". I'd be interested to see benchmarks on what practical effect this can have on the whole process.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: Wondering about File::Find by tye
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.