Before benchmarking and tuning, first try to profile your script, i.e. to find out where it "wastes" most of its time.
A good starting point may be the module Devel::Dprof (perl >= 5.003): just run your script with perl -d:DProf script.pl optionalParameters, which will produce a file tmon.out. Have a look at this file with the command dprofpp tmon.out
If this doesn't tell you things you didn't know, maybe Devel::SmallProf might be a finer approach.
Well, if you know (not guess) the parts that can be optimized, then try to find different Algorithms (require, open, ...) or Code and benchmark these (e.g. with Benchmark); but take care to benchmark a good representation of the data you work with, and not just some special values that might never come
Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"
Edit: g0n - fixed cpan links
In reply to Re: Using Perl files for options versus flatfiles?
by strat
in thread Using Perl files for options versus flatfiles?
by AK108
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |