× 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.



Could be that the chain/read version is I/O bound.  Embedded SQL can
compete with "some" native I/O Apps but "good" code using proper indexes
(LFS etc) can still beat SQL performance.  The benefits of using SQL
opposed to native I/O can be duplicated by creating LFs that contain
only certain fields from the PFs, etc.  But that comes at a cost as
well. 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Yivi
Sent: Thursday, November 17, 2005 5:24 PM
To: RPG programming on the AS400 / iSeries
Subject: crazy embedded sql performance

Hi everybody.

Recently I converted a rather simple program from using old style
chain/reade over lfs operations to embedded sql queries, which I find
prettier even if they have to be coded breaking free-format.

The thing is that I am getting a very steep difference in performance
between the two versions, with the SQL one completing the same tasks in
about a third of the time than the old one.

I am not complaining about the 40 minutes gained, but I was rather
afraid
that the change would bring a penalty in performance, and not a bonus. I
am
still skeptic, and tend to believe something is very wrong with the
chain/reade version, even if looks good to the eye and gives the right
results.

Anyone else had a similar experience? Or I am in the right track with my
lack of faith?

Regards,

I.-

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.