Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: how 8.1.7.4 calculates the # of 'library cache' latch children ?

Re: how 8.1.7.4 calculates the # of 'library cache' latch children ?

From: Joel Garry <joel-garry_at_home.com>
Date: 25 Nov 2003 16:17:20 -0800
Message-ID: <91884734.0311251617.2541ac3e@posting.google.com>


alberto.dellera_at_bigfoot.com (Alberto Dell'Era) wrote in message news:<f4ed41c5.0311250712.4124d566_at_posting.google.com>...
> Does anybody know how the number of 'library cache' latches are
> determined by the 8.1.7.4 kernel ?
>
> Yesterday we had 11 children and today we have 17 of them, after
> (1) upping the shared_pool dimension from 150M to 400M
> (2) increasing cpu_count from 10 to 14

Look in the server reference manual. It says, "If there is heavy contention for latches, change the value of LOG_SIMULTANEOUS_COPIES to twice the number of CPUs you have. Do not change the value of CPU_COUNT."
>
> Which one (or other) caused the birth of the 6=17-11 children ?
>
> This is very relevant to us since a f#@%ing third-party applications
> overparses millions of statements (no bind variables, parse
> once-execute once ...) and, until they solve the problem (in 2020AD I
> guess), i would like to limit the damage by at least increasing that
> number.
>

Please post your latch contention information like v$latch_misses so we can advise you correctly.

Also see http://www.ixora.com.au/scripts/latches.htm

jg

--
@home.com is bogus.
http://www.signonsandiego.com/news/uniontrib/tue/business/news_1b25boeing.html
Received on Tue Nov 25 2003 - 18:17:20 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US