RE: JT400/JDBC performance issues -- JAVA400-L

The toolbox driver, in my experience, is slower than the native driver (a
different server job), but 20 minutes response time can hardly be attributed
to the driver - it may have someting to do with the actual SQL requests.

Lo

-----Original Message-----
From: Mark Phippard
To: java400-l@xxxxxxxxxxxx
Sent: 2003.02.19. 13:00
Subject: Re: JT400/JDBC performance issues


You should send replies to the list, there are a lot of people on the
list,
including IBM'ers that could help.

As far as I know, the JDBC driver in the toolbox talks to the exact same
server job as the ODBC driver, so there should not be any LIC issues.
To
be safe, I would make sure I was using a version of the toolbox the
claims
to support V4R4.

You sure that the slowdown is not in building the XML DOM?



      To:   <MarkP@xxxxxxxxxxxxxxx>
      cc:   <joepluta@xxxxxxxxxxxxxxxxx>
      bcc:
      Subject:    Re: JT400/JDBC performance issues
"Suresh kumar BV" <suresh@xxxxxxxxxxxxxxxxxx>

02/19/2003 07:25 AM ZE5B
            <font size=-1></font>





















Hi Mark,
First of all thanx for the immediate reply. Servlet simply does the
following (we have stripped it down):
- get the connection string (AS400JDBCDRiver)
- Do the SQL: it is a simple Select col 1, 2, 3 from a <table>. This
table
has approx 100 records in total and we probably are selecting 20 of
them.
- Create an XML DOM of this hierarchical data that I got from AS400
-- Paint a HTML screen based on this data.

While testing we put the trace and it seems to connect to AS400 pretty
fast. However, the trace after the SQL statement takes for ever. So, it
looks like the SQL statement is creating the delay.

At the same time, if I query the same table in client access the result
is instantaneous. That's why my question was do I need to install some
LIC
PGM on the AS400? OR can we monitor this on AS400 as it runs? Hope this
helps.

Suresh

----- Original Message -----
From:"Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>
To:Java Programming on and around the iSeries / AS400
<java400-l@xxxxxxxxxxxx>
Subject:Re: JT400/JDBC performance issues

>
> Suresh,
>
> To get performance that bad it seems like it would have to have
> something
> to do with the JDBC statements you are executing.  Are you using SQL
> Views
> in your SELECT?  Generally, these perform worse than Tables on the
> iSeries.
>
> You do not mention how large your tables are or how many records you
are
> selecting.
>
> Finally, once those issues are worked out, a big area where problems
> will
> occur with the iSeries is if you do not use Connection Pools.
> Establishing
> a connection to the iSeries has a high overhead.  Using a pool
> eliminates
> that problem.  However, we are talking seconds not minutes.
>
> Hope this helps,
>
> Mark
>
>
> _______________________________________________
> This is the Java Programming on and around the iSeries / AS400
> (JAVA400-L) mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>



Antares Systems Ltd.
# 24, Sudha Complex, 3rd Stage, 4th Block,
Basaveshwaranagar,
Bangalore - 560 079
Telefax : 91-80-3284311, 3284313






_______________________________________________
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.