Hi Stas,
Am Montag, 16. Februar 2004 11:58 schrieb Stas Bekman:
Boris Zentner wrote: [...]
It works better, but not right. It has the same problems as the last one, but the other way around ;-)
On my first test I found out that it is incredible slow. So iI move the
return if $AUTOLOAD =~ /$skip/;
line before the lookup_method. That is not right ever, your way looks much better, but it was so slow. Perhaps other ideas are around.
What's slow? Are there too many calls to DESTROY? Can you add tracing to figure out the reason?
It was so slow that I thought it is not working at all. Yes it was eval and destroy. But I take a closer look later.
Users who are after performance must not be penalized with this module being preloaded. So it should be configurable, with default to be On.
We probabably can instrument EazyLife to dump a list of modules, that it has loaded during the scripts execution, on the server shutdown, to make it easier for the users to know which modules to preload and eventually get rid of EazyLife.
PerlEazyLife <Off|On|OnInfo>
Also another way to deal with DESTROY calls is to autovivify them as noops.
my $noop = sub () {};
...
goto &$noop if /DESTROY$/;or even:
use constant NOOP => ''; ... goto &NOOP if /DESTROY$/;
does this speed things up?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
