in reply to Optimization Help on Perl Hash Traversal (eval use)
The idea behind the eval blocks is to add a layer of abstraction so that when I need to add additional statistical analyses I can add entries to mysql with the proper eval string.
The most effective optimisation would be to avoid (re)-evaling your snippets for every id.
And the easiest way to do that would be to construct your snippets so that they can be eval'd into subroutines once each, and then you can call the appropriate subroutine for each ID instead.
As you haven't posted your snippets, I can't offer a realistic example, but by way of giving you an idea, something line:
$_ = sub{ $_ } for keys %{$agg_snippets};
Would (assuming the snippets are correctly defined, turn the snippets into subroutines.
You then just invoke the appropriate subroutine passing the data as arguments; and your code should run substantially faster.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Optimization Help on Perl Hash Traversal (eval use)
by mwb613 (Beadle) on Feb 06, 2013 at 22:32 UTC | |
by BrowserUk (Patriarch) on Feb 07, 2013 at 01:52 UTC | |
by mwb613 (Beadle) on Jun 04, 2014 at 00:39 UTC | |
Re^2: Optimization Help on Perl Hash Traversal (eval use)
by Anonymous Monk on Feb 07, 2013 at 01:28 UTC |
In Section
Seekers of Perl Wisdom