× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Erich W. Schasse
> 
> Joe,
> 
> what's about SELECT INTO ?
> 
> I'm sure, the ratio would no longer be 6:1.

Excellent, Erich!  This is the kind of thing I like to see!  It indeed
lowers the time for the SQL 30%, down to seven seconds.  But that's
still much slower than the native I/O.

The interesting thing about my test is that the first time you run the
RPG test after a period of system quiescence, you get a value of about
20-30 seconds for 100,000 records.  The second time drops to 15 seconds.
The third time it drops to seven seconds.  My guess is that this is
related to how DB2 caches data, since the performance improvement is
shared by others jobs.

However, no such effect occurs for the SQL.  The result is seven seconds
for 10,000 records, no matter what.

So, with repeated calls, the native I/O increases in speed from three
times the speed of SQL to ten times the speed.  I have no good answer
explanation for this, I'm just relaying the information.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.