Aaron Bannert wrote:
Just so I understand the problem correctly,
but that since the turnover is so quick you end up having children lingering around with one or two thread slots and essentially we approach the prefork scenario in terms of number of child processes. Is this correct?
in worker + event there is also the "squatting" logic where newly spawned children take over partially empty scoreboard slots in a non-intuitive manner. so excessive killing & spawning can lead into strange code paths and Bad Things that can't happen in prefork.
Greg
