Hello all,
I have a major Perl program which does a lot of SQL queries. In the past I
would time each query using Time::HiRes like this:
$t0 = [gettimeofday];
# do SQL query and stuff
$t = [gettimeofday] - $t0;
print "DEBUG: time elapsed is $t\n";
The issue is,
1) I just rewrote the guts of this program because we did a major
redesign on our schema
2) the program is unacceptably slow now
I don't want to insert Time::HiRes instrumenting code all over the place
again. Unfortunately, Devel::DProf doesn't give me line-by-line execution
time breakdowns, and Devel::SmallProf has a clash somewhere with
DBD::Oracle so running my program with -d:SmallProf causes it to crash.
Are there any other ways I can profile my program to determine which SQL
queries need to be optimized? I did a quick-and-dirty of the SQL, and I'm
in no mood to optimize them all.
--
Orlando Andico <[EMAIL PROTECTED]>
Mosaic Communications, Inc.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d(-) s: a-25 C++++ UBLSI++++$ P+++ L+++>++++ E- W++ N(+)
o K? w O-- M- !V PS(++) PE- Y PGP-- t(+)@ 5(+) X++@ R(+) tv@
b++ DI++ G e++@ h--(*) r% y+
------END GEEK CODE BLOCK------
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
