in reply to Re: Best way to do caching of Class::DBI objects from a MySQL database
in thread Best way to do caching of Class::DBI objects from a MySQL database

I'm not denying that Class::DBI will be slower than using straight DBI but in most cases this doesn't matter.
Hm... "most cases". What kind of "most cases" are you thinking of? Have you used Class::DBI on a heavily loaded web site, for example?
And where it does matter, you can step outside of C::D and just use DBI and SQL.
Do you have any suggestions on how you would find out when it matters? Any hints on profiling a Class::DBI app?
  • Comment on Re^2: Best way to do caching of Class::DBI objects from a MySQL database

Replies are listed 'Best First'.
Re^3: Best way to do caching of Class::DBI objects from a MySQL database
by mpeters (Chaplain) on May 02, 2005 at 13:36 UTC
    Hm... "most cases". What kind of "most cases" are you thinking of? Have you used Class::DBI on a heavily loaded web site, for example?
    "most cases" == most websites. Most websites are not heavily loaded. But even on heavily loaded websites, it's still usually a minority of the code that gets hit the most.
    Do you have any suggestions on how you would find out when it matters? Any hints on profiling a Class::DBI app?
    Find the most visited portions of the application (that's what server logs are for) and then profile it just like you would any normal web application. Like this for instance.
[reply]

In Section Seekers of Perl Wisdom