Yesterday, after I started major rewriting of some session, user auth, logging and such in a mason application into the wonderful 'MasonX::WebApp' (Thanks Dave.), I realized that it would be nice to know what the performance impact is/was. Well on my dev system, I had moved the logging initialization and the L10n support into the new library along with already changing the apache configuration and updating the autohandler. After cursing like a good ol' sailor (poor guys get attributed with such things), I wished I was smarted and thought of running performance benchmarks before I had already pretty heavily change the current version... Nothing quite like hide-foresight... Well I broke down and figured out how to reload the old system and then found the very useful WWW::Mechanize::Timed to do some simple page response times (that is really all I care about). But it would have saved an afternoon if I had thought of it before starting to change the software over...
So as Pilon would say there is a lesson in every story, you can find you own here.
BTW, if you are writing apps with HTML::Mason check out the MasonX::WebApp it is a very useful library.
