Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> please help analyzing a runstats report
What is troubling me here is that run2 is using only 5% of the consistent gets that run1 does. I thought consistent gets was the most important statistic for queries?
All of the logical I/Os of run2 are smaller, but overall run1 uses less resources. I've run this a few times so the queries are compiled and its not factoring in parsing.
QL> exec runstats_pkg.rs_stop(500);
Run1 ran in 4455 hsecs
Run2 ran in 4040 hsecs
run 1 ran in 110.27% of the time
Name Run1 Run2 Diff LATCH.cache buffers lru chain 1,904 1,391 -513 LATCH.multiblock read objects 462 1,169 707 LATCH.session idle bit 6,150 7,045 895 LATCH.checkpoint queue latch 4,791 6,557 1,766 LATCH.enqueues 4,612 6,592 1,980 LATCH.messages 18,793 21,623 2,830 STAT...Cached Commit SCN refer 5,691 9,110 3,419 STAT...buffer is not pinned co 5,879 9,415 3,536 STAT...no work - consistent re 5,964 9,710 3,746 LATCH.session allocation 8,890 12,845 3,955 LATCH.library cache pin alloca 13,302 18,089 4,787 LATCH.sequence cache 10,596 15,389 4,793 LATCH.simulator hash latch 5,311 10,225 4,914 LATCH.undo global data 14,089 19,874 5,785 STAT...table scan blocks gotte 5,874 0 -5,874 LATCH.row cache enqueue latch 8,571 15,301 6,730 LATCH.row cache objects 21,791 33,373 11,582 LATCH.redo allocation 42,806 60,353 17,547 LATCH.shared pool 43,828 61,702 17,874 LATCH.dml lock allocation 43,880 63,303 19,423 LATCH.enqueue hash chains 59,423 85,041 25,618 LATCH.cache buffers chains 594,437 620,207 25,770 LATCH.library cache pin 79,556 113,499 33,943 LATCH.library cache 99,851 140,603 40,752 STAT...buffer is pinned count 82,183 149,898 67,715 STAT...table fetch by rowid 2 79,600 79,598 STAT...index fetch by key 82,187 2 -82,185 STAT...table scan rows gotten 82,185 0 -82,185 STAT...session logical reads 170,885 10,383 -160,502 STAT...consistent gets 170,353 9,845 -160,508 STAT...consistent gets - exami 164,381 15 -164,366 Run1 latches total versus runs -- difference and pct Run1 Run2 Diff Pct
PL/SQL procedure successfully completed.
![]() |
![]() |