Re^4: File::find preprocess problem

I don't understand why so many folks like these other modules when a simple find() will often do the job!
I guess the documentation could be improved?

File::Find is a core module and it runs really fast. My hint about this special underscore variable -> that can make a big difference. It took me awhile to learn that "trick", but I very sure that this is true. That is basically about a 2x performance increase if you are doing 2 file tests.

The overhead to call a subroutine with no args (which is what find() does), is pretty much nothing compared with a file system operation.

I'm not sure that running \$preprocess even helps in OP's application. Weirdly enough, it may actually be slower due to the processing before calling \$wanted(). But this depends upon how many files/directories are underneath the /advanced/ path's and whether pruning these descent path's out from the directory descent really helps. Also how significant are the number of simple files that are not log files? Maybe these are huge in number to the .log files, maybe not.

From my experience, the single thing that will drive the performance, is the number of stat(), file system operations.

Comment on Re^4: File::find preprocess problem

Replies are listed 'Best First'.

Re^5: File::find preprocess problem
by Anonymous Monk on Apr 27, 2012 at 14:16 UTC

I don't understand why so many folks like these other modules when a simple find() will often do the job! I guess the documentation could be improved?

Sure you do : It is tons easier, requires less brain power to use, has a more memorable interface

When is the last time you saw a question about how to use File::Find::Rule or Path::Class::Rule?

?node_id=3989;HIT=File%3A%3AFind%3A%3ARule;re=N

Found 11 nodes roughly between 2012-04-27 and 1999-10-04 (searched 100.00% of DB).

where title contains "File::Find::Rule"

2012-01-12 ewittry Help on File::Find::Rule Please SoPW

2011-06-28 Anonymous Monk Using file::find and file::find::rule inthe same perl script is giving a warning SoPW

2010-10-15 eff_i_g Stopping File::Find::Rule SoPW

2009-11-10 Win File::Find::Rule - error message with use of SoPW

2009-07-31 Win use File::Find::Rule SoPW

2008-04-21 vatheck trouble getting complex File::Find::Rule search working SoPW

2007-12-19 leocharre Is there a way to set max results on File::Find::Rule? SoPW

2007-05-25 leocharre how to get File::Find::Rule to match empty directories SoPW

2004-10-27 Anonymous Monk Can't locate File::Find::Rule in @INC SoPW

2004-07-20 neniro Using -mtime in File::Find::Rule seems to fail on Windows SoPW

2003-08-19 annie Issues with File::Find::Rule 'not_name' rule SoPW

?node_id=3989;HIT=File%3A%3AFind%20;HIS=%3B;re=N

Found 50 nodes roughly between 2012-04-27 and 2005-08-24 (searched 49.73% of DB).

Found 50 nodes roughly between 2005-08-24 and 2001-09-24 (searched 38.44% of DB).

Found 20 nodes roughly between 2001-09-24 and 1999-10-04 (searched 11.82% of DB).

Gee, 11 versus 120, and that is just on perlmonks

[reply]

Re^5: File::find preprocess problem
by zentara (Cardinal) on Apr 27, 2012 at 14:48 UTC

I don't understand why ..... a simple find() will often do the job...File::Find is a core module and it runs really fast

Just look at the discussion in this node, and you have your answer. :-) It needs a cookbook of runnable examples.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

[reply]

Re^5: File::find preprocess problem
by Anonymous Monk on Apr 28, 2012 at 03:07 UTC

&File::Find::wanted

[reply]
[d/l]

Re^6: File::find preprocess problem

by Anonymous Monk on Apr 28, 2012 at 04:07 UTC

Rot I thus: I certainly do not feel compeled ...

Well, I feel strong enough now to note that correct spelling of the last word above should be "compelled".

[reply]