Class::DBI follows all of the DBI best practices for performance. Separating fields into different databases for performance reasons is a very specialized task that no general tool is ever going to do for you. In general, Class::DBI can be helpful to performance because it implements things like lazy-loading that most people don't bother to do when they write their own database access objects. | [reply] |
Sorry, it was late last night when I posted that, I just meant to state that Class::DBI, being a general use layer, can never be as fast as well written specialized DBI and SQL. I was assuming that the OP may come back with an issue about blob fields in the same database being too unoptimized. I agree with you 100%.
| [reply] |