Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Using a Large Oracle Blocksize

Oracle Database Tips by Donald Burleson

When Oracle first introduced segregated data buffers (each sized for a different tablespace blocksize), it opened-up a whole new world of possibilities for the Oracle tuning professional.

Today, multiple blocksizes are used in world-record performance benchmarks, and you can click here to read about real-world applications of large Oracle block sizes.

Going with small blocksizes:

For high-update objects (lots of insert, updates and deletes) many Oracle professionals segregate these into a small data buffer to relieve stress of the DBWR background process.

Random fetches of small table rows can also be segregated into a 2k tablespace so as not to waste RAM data buffers when you are only seeking small rows with single-row fetches.

Going with large Oracle blocksizes:

Robin Schumacher recommends a 32k block size for Oracle index tablespaces to keep the tree structure flat and to facilitate index fast-full scans and index range scans with less I/O.

As a general rules, Oracle professionals seek large blocksizes for indexes and objects that are the target of full table scans (i.e. db_file_multiblock_read_count) because more data can be fetched between physical I/O's. Kevin Loney also recommends large Oracle blocksizes except in high-DML conditions:

"There is only one reason not to use the largest block size available in your environment for a new database: if you cannot support a greater number of users performing updates and inserts against a single block. Other than that, increasing the database block size should improve the performance of almost everything in your application. Larger database block sizes help keep indexes from splitting levels and help keep more data in memory longer."

For more on leveraging large Oracle blocksizes, see my latest book "Oracle Tuning: The Definitive Reference". 

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational