Re: ASSM and high volume concurrent inserts
- From: Surachart Opun <surachart@xxxxxxxxx>
- To: Oracle-L@xxxxxxxxxxxxx
- Date: Fri, 18 Dec 2009 01:21:10 +0700
- Allocate size Table on tablespace (avoid extend tablespace by auto)
alter table ... allocate extent ...
or create use tablespace specify extent size(create tablespace with uniform
extents)
- Partitioning Table/Index
- Enough ITL on the block (INITRANS)
- No Indexing
- No integrity checks (Foreign keys, not null constraints)
- Increae Buffer cache (if it's to small you'll early end up with I/O)
Good Luck
Surachart Opun
http://surachartopun.com
On Fri, Dec 18, 2009 at 12:46 AM, Haroon A. Qureshi <
haroon_a_qureshi@xxxxxxxxx> wrote:
> Hello,
>
> A client is running an application that does high volume concurrent inserts
> (> 200million rows). Performance degrades with high buffer busy waits. The
> tablespace is ASSM managed, so we can't change the freelists to tune it. I
> want to try moving to a manually managed tablespace and tune the freelists.
> But not sure if the client will go for that change, given the effort and
> timelines. Has anyone come across performance issues with ASSM and high
> volume inserts? Anyway of tuning it with ASSM?
>
> Thanks in advance,
> Haroon
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
Other related posts:
