RE: Operations that perform multiblock I/O and cluster factor

From: Riku Räsänen <riku.rasanen@xxxxxxxxxxxxxxxx>
To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
Date: Tue, 11 Dec 2007 20:45:07 +0200 (EET)

Ah, sorry, too tired. And it actually wasn't doing a range scan (not now nor in 
the past), it was
doing a index full scan.

STAT #6 id=1 cnt=1000000 pid=0 pos=1 obj=10627 op='TABLE ACCESS BY INDEX ROWID 
CLUSFAC_DEMO
(cr=1001382 r=1000000 w=0 time=96322038 us)'
STAT #6 id=2 cnt=1000000 pid=1 pos=1 obj=10629 op='INDEX FULL SCAN 
IDX_CLF_SCATTERED (cr=1382 r=0
w=0 time=5124467 us)'


> My guess is that the p3=40 is due to the hiddden parameter setting 
> _table_lookup_prefetch_size=40

The guess is correct.



-- 
Riku Räsänen
Kantamestarit OY
www.kantamestarit.fi

--
http://www.freelists.org/webpage/oracle-l

References:

Operations that perform multiblock I/O and cluster factor
From: Josh Collier

RE: Operations that perform multiblock I/O and cluster factor
From: Allen, Brandon

RE: Operations that perform multiblock I/O and cluster factor
From: Riku Räsänen

Re: Operations that perform multiblock I/O and cluster factor
From: Alberto Dell'Era

Re: Operations that perform multiblock I/O and cluster factor
From: Riku Räsänen

RE: Operations that perform multiblock I/O and cluster factor
From: Allen, Brandon

RE: Operations that perform multiblock I/O and cluster factor

Other related posts: