RE: ASSM and high volume concurrent inserts
Date: Thu, 17 Dec 2009 18:14:42 -0500
Message-ID: <4b2abb54.9553f10a.501c.ffffc36c_at_mx.google.com>
Not sure what you mean by 'manually managed'. To manage FLists yourself, you need a DMT TS, which I believe can't do in 10g (for read/write). We had a similar problem on a high frequency LOB insert, which we resolved by eliminating a composite unique constraint. About 90% of BBW's that I've seen resulted from poor application design or run-time anomalies. Focus on application design and run-time behavior before you start thinking tablespace and segment attributes.
-----Original Message-----
From: Haroon A. Qureshi <haroon_a_qureshi_at_yahoo.com>
Sent: Thursday, December 17, 2009 12:46 PM
To: Oracle-L_at_freelists.org
Subject: ASSM and high volume concurrent inserts
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
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Dec 17 2009 - 17:14:42 CST