On Tue, 15 Oct 2002, Henri Asseily wrote: > In the case of db profiling, I tell it to overload DBI::st::execute > with a profiling method that does the following:
The DBI::Profile interface actually profiles every DBI method, connect(), prepare(), execute(), fetch() and everything in-between. As a result it can provide profiling data on the entire time spent on a given statement. This is useful for correctly measuring the time taken in SELECTs that return large result sets where fetch() time is significant, for example. > The module is totally generic, allowing for dynamic overloading of any > method in any package, and is perfect for mod_perl usage. > You can see from the code above that I capture the real time used for > the execution and write to a csv file. How do you analyze this data? Did you also write a front-end? > Let me know if you're interested in that simple module. I wouldn't mind taking a look; it's always interesting to see how another programmer tackles a problem. But I'm almost done with DBI::ProfileDumper and DBI::ProfileData so I doubt I would be able to use your code directly. Thanks, -sam
