RE: Anyone using multi-block sizes for their databases

From: Lex de Haan <lex.de.haan_at_naturaljoin.nl>
Date: Thu, 21 Jul 2005 18:51:54 +0200
Message-Id: <20050721165154.0BBF31D714E@turing.freelists.org>

Juan,

with all due respect, I believe this is *not* a good advice. I actually think it is a *bad* advice. you try to achieve something with the wrong technique, at a way too high price.

let me first say that the only *intended* reason for multiple blocksizes is to make transportable tablespaces more flexible. any other reason might have its merits, but should be considered with caution.

the biggest disadvantage of a segmented cache is that free space gets segmented too, obviously -- typically leading to much more memory wastage than with a single unsegmented buffer cache.

kind regards,

Lex.

Steve Adams Seminar http://www.naturaljoin.nl/events/seminars.html

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Juan Carlos Reyes Pacheco
Sent: Thursday, July 21, 2005 18:45
To: Oracle-L_at_freelists.org
Subject: Re: Anyone using multi-block sizes for their databases

Hi,
This works really nice, this allows to create separate areas of memory for different things.
For example big blobs documents, in a 32k normal tables 8k indexes 16k, etc. etc.

You have to set the database memory cache in the init.ora for each different block size.
--

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

--

http://www.freelists.org/webpage/oracle-l Received on Thu Jul 21 2005 - 11:53:55 CDT