In such a scenario, I would look at the manner by which the dispatch is ordered, seeking for any hierarchy which may be utilised to further define run-modes - I would then separate those group run-modes of similar functionality into separate dispatches. These separate dispatches could then be moved into separate scripts with a shared server-side backend where required.

If this was not possible, I would investigate the dynamic loading and unloading of module components through the use of the use and no module functions - This should allow memory to be allocated and freed as necessary but the details of whether this memory is returned to the system is dependent upon the runtime C library.

In any case, I would be incorporating the CGI::Application dispatch into the apache binary with mod_perl. Based upon the intended scope of the project described, the performance advantage of employing mod_perl cannot be ignored.

 

perl -le 'print+unpack("N",pack("B32","00000000000000000000001000100100"))'