in reply to Re^7: Any gotchas with CGI and Mouse running together?
in thread Any gotchas with CGI and Mouse running together?
But let's take it positive, and try to make an insightful post worth linking to.
Your Mother already convinced me that startup time wouldn't improve much and I'm not a M* user anyway.
So why don't you bench it? :)
FWIW some theory for those interested:
calling Moose->import() for each use Moose;
Naturally pre-compilation (like "perlcc Moose") can only effect phase 1, which is a one-time advantage.
But YM already pointed out that startup time grows significantly with the number of classes.
If you or anyone else is interested in benchmarking it, I'd suggest taking Schwern's test scenario and extend it appropriately to identify these phases.
¹) so what people actually mean is the resulting start up time of modules/classes build with Moose.
Of course one could try to benchmark the application of classes created with Moose, i.e. mainly creating objects and calling methods.
But that's not startup time anymore, and hearsay is that runtime is fast enough.
|Replies are listed 'Best First'.|
Re^9: Any gotchas with CGI and Mouse running together? (start up explained)
by Anonymous Monk on Mar 01, 2015 at 06:58 UTC
by LanX (Sage) on Mar 01, 2015 at 14:43 UTC
by Anonymous Monk on Mar 01, 2015 at 22:04 UTC