Prepared Statement Slow. ~Baffled~. Will the sun rise again?

Question

HELP! (PANIC), Disaster
Problem?: Its slow.
How can you help?: Explain why and make suggestions to fix it.
NOTES:
1) there are indices on pd_idnum and pd_nappi_product_id
2) over 92000 records in the product table
Code Follows:
import java.sql.*;
import java.text.SimpleDateFormat;
public class DBTest
static PreparedStatement pstmtNewNappi = null;
ResultSet rsNappi6=null;
Connection myConn = null;
int pd_idnum=0;
SimpleDateFormat sDateFmt = new SimpleDateFormat("yyyyMMdd");
SimpleDateFormat sTimeFmt = new SimpleDateFormat("hhmmss");
* Constructor for DBTest.
public DBTest()
super();
try
Class.forName("org.gjt.mm.mysql.Driver");
myConn = DriverManager.getConnection(
"jdbc:mysql://carl-lin:3306/mxprod", "carl", "lrac1234");
pstmtNewNappi = myConn.prepareStatement(
"SELECT pd_idnum FROM product WHERE pd_nappi_prod_id=?");
catch(ClassNotFoundException cnfe){cnfe.printStackTrace();}
catch(SQLException sqle){sqle.printStackTrace();}
public boolean isNewNappi(String nappi) throws SQLException
if(nappi != null)
pstmtNewNappi.setInt(1, Integer.parseInt(nappi));
System.out.println("before execute"
+new java.util.Date().getTime());
// This single line of code takes 2 seconds!! Why?
rsNappi6 = pstmtNewNappi.executeQuery();
System.out.println("after execute"
+new java.util.Date().getTime());
if(rsNappi6.next())
//if im in here the nappi is not new
pd_idnum = Integer.parseInt(rsNappi6.getString("pd_idnum"), 10);
return false;
return true;
public static void main(String[] args)
try
DBTest dbt = new DBTest();
boolean yes = dbt.isNewNappi("43");
System.out.println("yes: " + yes);
catch(SQLException sqle)
sqle.printStackTrace();
Maybe PreparedStatements are only fast for inserts(Forgive me for guesing)
Any help would be greatly appreciated

Answer 1

Oh that came back like lighting allright but i got my hands on some more code here that (if my reasoning is correct) suggest that I'm using the prepared statement in the wrong way, but I can still not figure out why it is wrong. The DB is not the problem and I think the code below and its output is testament to that. Now that i've got fast code, I'm still not content because I still cant see what is wrong with the original code. In order for me to keep my sanity as a programmer I HAVE to know --WHAT IS WRONG aaaargh
Thanx for the help so far
Dewet
optimal code follows:
import java.sql.*;
public class Fix
public static void main(String[] args)
ResultSet prodSet = null;
String nappi = null;
String sql = null;
try
Class.forName("org.gjt.mm.mysql.Driver");
Connection myConn = DriverManager.getConnection("jdbc:mysql://carl:3306/mxprod?user=carl&password=lrac1234");
sql = "select pd_prod_name, pd_prod_name_mk from product where pd_nappi_prod_id = ?";
PreparedStatement stmt2 = myConn.prepareStatement(sql);
nappi = "43";
for (int i= 0; i < 10; i++)
               System.out.println(i);
System.out.println(new java.util.Date().getTime());
stmt2.setString(1, nappi); // Nappi
prodSet = stmt2.executeQuery();
if(prodSet.next())
{*nappi found*/}     
System.out.println(new java.util.Date().getTime());
if (stmt2 != null) stmt2.close();
myConn.close();
catch( Exception e )
e.printStackTrace();
output:
0
1055320536664
1055320536694
1
1055320536694
1055320536694
2
1055320536704
1055320536704
3
1055320536704
1055320536714
4
1055320536714
1055320536714
5
1055320536714
1055320536714
6
1055320536724
1055320536724
7
1055320536724
1055320536724
8
1055320536734
1055320536734
9
1055320536744
1055320536744