LOCALLY MANAGED EXTENT PERFORMANCE

  • From: Wolfson Larry - lwolfs <lawrence.wolfson@xxxxxxxxxx>
  • To:
  • Date: Fri, 22 Apr 2005 23:24:12 -0500

Hi guys!
        
        Anyone seen any issues with large locally mananged extents?

        Recently I noticed one of my applications taking a long time to do
truncates.
        
        And an index rebuild where I increased the locally managed extent
size from 16K took almost an hour for 58,000 extents when larger indexes
(and extents) only took 3-4 minutes.

        I once had a purchased app using a 16K extent size for huge tables
took 2 hours and 7 minutes to do a truncate on just one table (dictionary
managed).  I killed it the first time after 45 minutes cause I thought it
was hung up somewhere else.
        Not sure why it was set to 16K in the first place.  Good for testing
I guess.

        Thanks
        Larry

        


**********************************************************************
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.

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

Other related posts: