1.2 million gets per execution as reported in AWR. :-)
On Tue, Jun 19, 2018 at 3:13 AM, Harel Safra <harel.safra@xxxxxxxxx> wrote:
Is this 1.2M gets in total or for each query?
Load Runner can run the same scenario with this query multiple times in
different sessions - 1.2M gets in total is just 24 threads running it in
parallel
On Mon, Jun 18, 2018 at 9:49 PM Ashish Lunawat <ashish.lunawat@xxxxxxxxx>
wrote:
Hi, I have a query which when run through autotrace and tkprof shows me
about 50,000 gets. But the same query when shot as a part of loadrunner
performance testing causes about 1.2 million consistent gets as seen in the
AWR report. How is this possible?
The database is running on a 2 node RAC with each node having 32 cores.
Tkprof shows this query takes about .8 seconds and causes 50K consistent
gets while when shot through loadrunner it, causes both the RAC nodes to go
as much as 100% CPU. When monitoring session waits I can see that there is
a hot block contention happening on a table with about 19K rows and an
index on this table. This query is responsible for about 94% of the gets
and thus high cpu utilization.
Any clues how to troubleshoot this issue?
Thanks
Regards,
Ashish
