Date: Sat, 5 Sep 2009 04:42:42 -0700 (PDT)
11.2 has introduced instance caging where you can limit cpus used by an instance by setting cpu_count
From New Features Guide
220.127.116.11 Instance Caging
Instance Caging allows the DBA to limit the CPU usage of an Oracle instance by setting the CPU_COUNT initialization parameter and enabling CPU resource management.
With Instance Caging, users can partition CPU resources among multiple instances running on a server to ensure predictable performance.
On 4 Sep, 19:24, John Hurley <johnbhur..._at_sbcglobal.net> wrote:
> On Sep 4, 2:09 pm, Sue <suesch..._at_gmail.com> wrote:
> > Does anyone know what CPU_COUNT means on a mulit-core machine? Say
> > you have a four core cpu. Does setting CPU_COUNT to 1 use all 4 cores
> > on 1 CPU or 1 core on a CPU?
> Each core looks like to oracle a cpu ... this is not a throttling or
> hard/soft partitioning mechanism.
> Never heard of anyone trying to set it directly ... oracle picks it up
> from the operating system.
> If you have a system that does some kind of hard partition of cpu
> resources then oracle only see's what is available in that partition
> ( so sets CPU_COUNT correctly ).
> There's a bunch of info in metalink on this ...
Received on Sat Sep 05 2009 - 06:42:42 CDT