Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Table scan and LRU caching

Re: Table scan and LRU caching

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Tue, 26 Sep 2000 12:46:12 +0100
Message-ID: <8qq2a5$92g$1@soap.pipex.net>

"Bastorff" <nospam_at_localhost.zz> wrote in message news:_VPz5.13751$Fl2.120645_at_nntpserver.swip.net...
> "Brian Peasland" <peasland_at_edcmail.cr.usgs.gov> wrote in message
> news:39CFBF4B.BB31840D_at_edcmail.cr.usgs.gov...
 

> When do blocks get placed not at the MRU end (when first
> fetched)? Do blocks age off towards the LRU end unevenly?
>
> Regards,
> /fad

Blocks read by rowid (i.e. indexed scans get put at the mru end). Bear in mind as well that most frequently used bblocks should always be in memory, since the block will continue getting bumped back up the mru list by the lru algorithm.

hth

--
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Tue Sep 26 2000 - 06:46:12 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US