Not necessarily, that would be your MAXIMUM number of simultaneous
connections, unless you connect to all the datababases when a children
is spawn (which would be pretty dull methinks, I prefer lazy
algorithms).

Well, it's going to be a pretty strange environment that doesn't have a database connection in every process. After a certain number of requests, you can pretty much be assured that your database application has been hit in every process and therefore every process has a connection. Thinking of it as just the maximum is semantically correct, but in reality, thinking of it as your common load is the best practice.

Kenny Smith



Reply via email to