Why not set --idle-children at start-up to something higher (or just 0 to disable)?
Setting it higher is a bit bothersome because our QP children use too much memory right now (mainly from using DBIx::Class), so it would be a bit unfortunate to have more memory-consuming kids around that aren't needed. As for disabling idle-children.. what exactly would the behavior be with disabled idle children? In a situation where concurrency is saturated, it seems that QP spawns $idle_children processes every $loop_wait seconds. Would QP instead spawn a new child _immediately_ when a new connection attempt came in? Or if it still waits $loop_wait seconds, how many children does it spawn when it sees some are needed?
-Jared
