RE: SQL Insert -- JAVA400-L

It's possible that changing the driver may speed things up, but I believe
that there is some other problem here. I am running a small internal website
on a PC server, with a not very recent version of JT400, and for a servlet
to do a retrieval (usually less than 1000 records) and reformat it using an
XSLT transform typically takes only a couple of seconds. It's using a
connection pool, so there shouldn't be any connection time in that couple of
seconds.

It isn't necessary to speculate on how long things are taking. You have
already done some measuring on the AS/400 side. A little bit of logging
would tell you just how long it takes the servlet to retrieve and process a
result-set, or to make a connection, and if you use Mozilla as your browser
it tells you just how long the entire request-response turnaround took.

Regards
PC2

-----Original Message-----
From: Alex Pinsky [mailto:apinsky@xxxxxxxxxxxxxxx]
Sent: April 7, 2003 13:46
To: Java Programming on and around the iSeries / AS400
Subject: RE: SQL Insert


Hi Suresh,
I'd recommend you to try different JDBC driver. Try one from HIT Software at
http://www.hitsw.com/products_services/sql400/jdbc400/jdbc400.html
They offer free of charge evaluation version and very good tech support. We
tried one and we've got noticeable performance improvement.
We didn't buy one because we moved our app server to AS/400 and now use
'native' JDBC for data access (which is even better)
Alex

-----Original Message-----
From: Suresh kumar BV [mailto:suresh@xxxxxxxxxxxxxxxxxx]
Sent: Monday, April 07, 2003 3:28 PM
To: java400-l@xxxxxxxxxxxx
Subject: Re: SQL Insert


Hi Dieter,
   In the last week this is what we have done to find the possible bottle
neck in the system:

   We tried to run the application in isolation when almost the entire
system was at the disposal (9406-720, 2GB memory, 50% DASD utilization,
DZDASOINIT runs in machine pool etc...). This is what we have seen:

1. DB Monitor shows that actual SQL time is negligible. It takes about 1.8
seconds to perform SQLs involved (about 25 SQLs). We noticed that OPEN and
DE (I don't know what is this -- description??) operations seem to take
most time out of this 1.8 seconds. Question is how do we make the opens
reuse ODPs? In our case every SQL seems to do full open. Note that we are
using JT400 to access AS400 data from servlets which are running on a PC
Webserver. Other question is what is this DE record and how do I reduce the
overhead there??

2. Overall response time is about 15-20 seconds. We feel that once the data
is obtained by servlet it should not take more than 1-2 seconds to create
the HTMl with images and render the page. Where else is the time lost?? Is
this thanx to JT400?? Note that the high speed PC server and AS400 are on
the LAN next to each other.

Any suggestion would be helpful
Suresh