On 16-Dec-2015 08:13 -0600, Richard Reeve wrote:
Please excuse my ineptness where this subject is concerned. I am
trying to determine why a query that runs in less than a second
locally(IBM i) takes many seconds (more than 10) when done through a
web page connected to said IBM i. It is a basic udl connection.
Any ideas on where I should be looking or a guide book to follow?
Thanks for any suggestions. Have a great day!
I did not look at the article from Kent pointed out by Charles, but
the simplest for the described effect would be to code an OPTIMIZE FOR
10 ROWS clause on the query [as a hint to the optimizer that the
/optimization goal/ alluded in a prior reply, is explicitly on par with
*FIRSTIO vs *ALLIO; as just a clause, that is accmoplished without any
modification to any connections\initializations\et al]. And if the
query request is known to be read-only, then adding the clause FOR READ
ONLY is an option as well; some client interfaces might perform a query
with FOR UPDATE presuming the user-intention is to access the rows for
update rather than merely reporting, though I do not expect that is an
issue for the i Web Query.
This mailing list archive is Copyright 1997-2019 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