Profiling

Question

Hi all I have written an application that I am trying to make faster. It took approx 10seconds to completely execute and by simply passing a connection to all the methods reduced it to 6-7 seconds, while this is a decent improvement I want to get this running in < 1 second. My question is how can I find the biggest bottle necks ? I am currently using the crude manner of taking the system time at various points, which has helped me narrow the problem to one of two things - or at least I think it's one of 2 things. Either there is enough latency on the network to cause the problem (may explain some of it but not all) or more likely the fact that I am making roughly 60 prepared statements and then executing them is causing the problem. Any thoughts would be greatly appreciated.
EDIT
I have been using preparedStatements based on the information that they should be always used, but how much overheard is involved with them over a regular Statement ?
I was also looking but couldn't seem to find with a preparedStatement is it possible to have one statement with 3 parameters used for one query and then use the same statement but only using 2 of the 3 - Ie is there a way to say preparedstatement variables x y z
query 1)
x = 1
y = 2
z = 3
query 2)
x =1
y = 2
z (don't care)
It seems that preparing 2 statements took almost a 1/3 of a second which is unreasonable considering there are approx 30 others that have to be prepared, in what manners can I make this more efficient ?

Answer 1

My question is how can I find
the biggest bottle necks ? Using an automated profiling tool. Probably a commercial one.
I am currently using the
crude manner of taking the system time at various
points, which has helped me narrow the problem to one
of two things - or at least I think it's one of 2
things. Either there is enough latency on the
network to cause the problem (may explain some of it
but not all) or more likely the fact that I am making
roughly 60 prepared statements and then executing
them is causing the problem. Any thoughts would be
greatly appreciated.If you are using 60 prepared statements then you are making at least 60 seperate calls. Reduce the number of calls.
One way crude way is to make a stored proc that returns 60 separate result sets.
>
EDIT
I have been using preparedStatements based on the
information that they should be always used, but how
much overheard is involved with them over a regular
Statement ?For single calls a prepared statement will generally take more time than straight SQL.
I was also looking but couldn't seem to find with a
preparedStatement is it possible to have one
statement with 3 parameters used for one query and
then use the same statement but only using 2 of the 3Not exacly. You could of course make the statement conditionally use one parameter if it isn't null and not use it if it is.
Presumably you are using different first and second parameter values otherwise this is a waste of time.