Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re:os cache vs. db cache
Robyn,
Since you're running a data warehouse, you may want to consider the effects of parallel tablescans and parallel index fast full scans, which do direct path reads and bypass the buffer cache.
Of course, there are parallel execution paths that still USE the buffer cache (parallel nested loop joins with indexed access, access through partitioned indexes etc.) but if a very large percentage of the work you do is bypassing the Oracle cache, you may want to switch memory to the file system cache instead to try and keep some important objects "close to" the action.
Alternatively, you might think about putting the temporary tablespace onto a filesystem that has caching enabled so that blocks written to the temp tablespace are in the cache (and not on disc) when you start to re-read them.
Yet another option is to keep the caching low - depending on a SAN cache (for exanple) to help you with the TEMP space - and make as much memory as you can available for PGA activity so that you minimise the number of cases where sorts or hash joins spill to disc.
It's not a clear cut choice, unfortunately - often it's a question of observing the current activity and making the best guess about how moving memory around will benefit the critical processes.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 10 2007 - 11:50:20 CDT
![]() |
![]() |