You're actually reading and testing every entry in your directory, which probably accounts for your "disk activity". Directories with more entries will obviously take longer than others, especially heavilly loaded ones. There is no built in "filter" for readdir, to the best of my knowledge, so finding directories with subdirectories is going to be involved, even in the best circumstances.

Your second solution just reads in everything and then backtracks to find subdirs. If this is faster, then a native implementation of the "dir /ad /b" command might help you out.

If you query in an overlapping way, such that you are actually testing the same directory twice, caching your findings in a hash may save you the trouble of the test.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.