ETLp

 view release on metacpan or  search on metacpan

lib/ETLp/Manual/Install.pod  view on Meta::CPAN

=over 4

   1. Launching the Perl interpreter
   2. Compiling the code - including all dependent Perl libraries
   3. Initiate a connection to the database
   4. Perform the user request
   5. Exit
   
=back

With small applications on a non-busy site, this shouldn't cause any issues. However, it doesn't scale very well. Although ETLp Runtime Audit Browser isn't especially busy, it does requite many dependent classes.  In order to mitigate the issues abov...

=over 4

   1. When the first request is received, the Persistent Perl interpreter is launched.
   2. The code is compiled and a connection is made to the database.
   3. The user's request is performed
   4. Wait around for the next request
 
=back



( run in 0.313 second using v1.01-cache-2.11-cpan-3cd7ad12f66 )