|
What's the data look like between A & B?
Same total number of rows?
Same number of rows returned?
Recall that the system will basically always use arrival sequence if it
thinks more than xx% of the total will be returned... xx% is a relatively
low number, though I can't find it right now. I'm pretty sure it's less
than 30..actually 10% sticks in my head..
You might also check that the QAQQINI file in effect for the query is the
same on both systems.
Charles
On Fri, Aug 9, 2013 at 3:20 PM, Michael Ryan <michaelrtr@xxxxxxxxx> wrote:
Yes, B's performance is much poorer. Like a 2 second display build on Avs.
a 10+ second display build on Brunning
On Fri, Aug 9, 2013 at 3:08 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
Run Visual Explain from iNav's Run SQL scripts...to
But I'd be willing to bet the answer is "the cost to use this index was
high" or whatever the exact wording is.
Unless the systems are configured exactly the same, the query is
Iover the exact same data _AND_ the systems are running the exact sameSQE
workload at the time the query is done, there's no reason to assume the
would chose to use the exact same method.wrote:
Is the performance of system b significantly poorer?
Charles
On Fri, Aug 9, 2013 at 2:56 PM, Michael Ryan <michaelrtr@xxxxxxxxx>
Run
Ok...two systems, both on 7.1. Execute STRDBG UPDPROD(*YES). Run aprogram
on system A. Job log shows an index was used for bit map processing.
the same program on system B. Same index in place (though different
libraries). System B job log says arrival sequence was used. How can
mailingThanks!figure out why the index is used on one system and not the other?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listlistlist
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.