Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Large DB buffer, low cache hit ratio
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
news:94mldh$nf6$1_at_soap.pipex.net...
Hi Niall:
Ixora has a page on 'why large block size'. At it's top, it says :
QUOTE ON....
Because the database block size is fixed at database creation, this is one
decision that is important to get right the first time. For file system
based datafiles, without direct I/O, the database block size must match the
file system buffer size exactly, as explained in our tip Why Raw Datafiles.
For most Oracle databases under Unix, this means that the database block
size must be 8K (because the file system buffer size is invariably 8K).
However, if your database is raw, or if direct I/O is available, then you have the luxury of choosing a larger database block size. There are many advantages to using a large block size, but the most significant is the saving in I/O for index based access paths.
QUOTE OFF... NT uses direct I/O (at least as far as I remember), so the advice appears to means that NT block sizes should be bigger than 8K -which gets you to 16K (though I suppose 32K is a possibility. Never gone that big myself).
As to the relative sizes of Shared Pool and Buffer Caches... I can't find the particular document I was thinking of when I wrote that. All my Instances have started off that way -90M for the Shared Pool, 32M for the Buffer Cache (4000 x 8K). Of course, once you start tuning the thing, who knows how it will end up -that depends, obviously, very much on the type of hammering you give your Instance. But I've found this a reasonable starting point.
Regards
HJR
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
>
>
Received on Wed Jan 24 2001 - 14:42:33 CST
![]() |
![]() |