Re: Performance issue after creating higher block size tablespace
From: Jared Still <jkstill_at_gmail.com>
Date: Thu, 25 Feb 2010 09:31:18 -0800
Message-ID: <bf46381002250931t55798020s58e60b158e634d8f_at_mail.gmail.com>
On Thu, Feb 25, 2010 at 8:23 AM, Saad Khan <saad4u_at_gmail.com> wrote:
Date: Thu, 25 Feb 2010 09:31:18 -0800
Message-ID: <bf46381002250931t55798020s58e60b158e634d8f_at_mail.gmail.com>
On Thu, Feb 25, 2010 at 8:23 AM, Saad Khan <saad4u_at_gmail.com> wrote:
>
> The db_cache_size is set to 8192 and db_8k_cache_size is also set to 8192.
>
>
I don't know if you already considered this, but those cache sizes
provide differing number of blocks.
Assuming that 8192 refers to 8192M:
4k block
(8192 x 2^20) / (4 x 2^10) = 2097152 blocks
8k block
(8192 x 2^20) / (8 x 2^10) = 1048576 blocks
The cache for your new tablespace is providing half as many blocks as the default cache.
And as others have already stated, blocks sizes are not a tuning device.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 25 2010 - 11:31:18 CST