Re: DSS System -- db_cache_size and pga_aggregate_target
- From: "Greg Rahn" <greg@xxxxxxxxxxxxxxxxxx>
- To: hkchital@xxxxxxxxxxxxxx
- Date: Sat, 19 Jul 2008 23:22:02 -0700
This depends more on the detail of what you mean by DSS in terms of
workload. Are you using Parallel Query? Is the workload partition
scans and hash joins?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14223/usingpe.htm#sthref2504
"With the exception of parallel update and delete, parallel operations
do not generally benefit from larger buffer cache sizes. Other
parallel operations can benefit only if you increase the size of the
buffer pool and thereby accommodate the inner table or index for a
nested loop join."
On Sat, Jul 19, 2008 at 9:34 PM, Hemant K Chitale
<hkchital@xxxxxxxxxxxxxx> wrote:
>
> I have been informed that advice to increase the db_cache_size makes sense
> for an OLTP system but not a DSS system.
> That for a DSS system, the db_cache_size should not be large but the
> pga_aggregate_target should be large.
>
> Are there any "best practices" , "test cases", "white papers",
> "benchmarks" which indicate such ?
--
Regards,
Greg Rahn
http://structureddata.org
--
//www.freelists.org/webpage/oracle-l
Other related posts:
