> Cyrus does recycle processes. Unix forking is amazingly slow compared > to not forking and on servers that receive many connections a second > this performance tweak is vital.
That explains it; thanks for the explanation. (Still, even 10 forks/second seems entirely do-able. While I don't dispute the principle, I'd think you'd need to get closer to 100 forks/second before forking bottlenecks would become as important as disk I/O bottlenecks.)
