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

Just a couple of thoughts/suggestions:

Have you benchmarked your application? You describe it as 'sloooow' but do you *know* why it's slow or are you just assuming Class::DBI?
I'm not denying that Class::DBI will be slower than using straight DBI but in most cases this doesn't matter. And where it does matter, you can step outside of C::D and just use DBI and SQL. Also, there are many things that if done poorly with C::D can really cause performance hits (like sorting a result set in perl and not in your SQL). This is where profiling and benchmarking can really help. You would know exactly why it's 'sloooow'.
Are you using a custom db_Main()? It is sometimes usefult to override this method but you must be very careful since it's called *alot*. You must be careful that speed is always considered when changing it.

HTH

Comment on Re: Best way to do caching of Class::DBI objects from a MySQL database

Replies are listed 'Best First'.
Re^2: Best way to do caching of Class::DBI objects from a MySQL database by doom (Deacon) on May 01, 2005 at 18:03 UTC
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?	[reply]
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]