Thanks for the explanation. > A large system with upwards of 250 databases (on a relatively small > number of database machines) as part of the system, these are used by up > to a half a dozen web machines which can be forced up to a limit of 50 > children per machine... We regularly broke the connections limit on > our mysql instances! > > Alternative scenario - a single website this time with a small number > of databases but up to 50-60 developers each having their own sandbox > which needs access to these core sets of databases!
Ok, so both situations where you have many db logins. It makes sense that you wouldn't want to keep all the connections persistent then. There's actually a warning in the Apache::DBI docs about that scenario. And with MySQL connections you can skip persistence without taking much of a hit. Sorry to put you on the spot. There's been some FUD about Apache::DBI lately, and it's just better for the community to know whether something is actually broken or not. In this case, Apache::DBI worked as intended but it was wrong for the situation. - Perrin
