[Catalyst] Obtaining better application speed during development
Matt S Trout
dbix-class at trout.me.uk
Mon Mar 20 13:41:23 CET 2006
Michele Beltrame wrote:
> I use Catalyst with mod_fastcgi (when deploying) and with normal CGI
> (when developing).
> Execution of applications is getting however pretty slow even when
> developing, when solutions such as mod_fastcgi don't help as a reload of
> the application is needed (of course) after modifications to the code.
> What I am wondering is if a solution a-la-PHP exists, or does make sense
> at all: that is, the perl interpreter stays resident but the application
> doesn't. This would probably give limited benefits, but maybe limited is
> better than nothing (PHP is faster than plain CGI in almost all situations).
The problem is that Catalyst apps do their setup once at initialisation time,
so just reloading the changed code isn't always sufficient - as such the best
way to get a clean sheet after a change is a full reload.
You're welcome to try Apache::Reload, Module::Refresh and friends - I believe
provided you're using DBIx::Class rather than Class::DBI they work pretty
well, but bear in mind things like config changes and model setup events will
still need a full re-init to re-fire.
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
More information about the Catalyst