oracle大量local=no,excessive LOCAL=NO oracle processes

>

Does your narcissism know no bounds?

http://www.dba-oracle.com/t_narcissistic_personality_disorders.htm

If so, please post them, because, not being an

engineer myself, I reply on "real" experts. My

engineers (with degrees in electrical and computer

engineering from great universities) say that you

don't know what you are talking about.

It's not a claim, it's a fact, according to the folks

who built their servers!

The vendors who build the servers say that 100% CPU

utilization is optimal, and they wrote both the OS

and the underlying hardware.

http://www.dba-oracle.com/t_high_cpu.htm

Now I ask you, since you hide all evidence of having

any real-world job experience in this area, not to

mention your unsavory history of introducing bias

into your phony "proofs" to falsely discredit real

experts.

Why should anyone believe you?Don,

Of course you were bound to respond with ad hominem attacks, innuendo, and appeals to invisible authority figures.

You presented what you thought were supporting technical documents in the thread that I've already linked to. But as I pointed out there, both the documents you quoted actually explained why your '100% is optimal" is wrong.

Here are a couple of thoughts for you, however:

First: check the following simple example of how wrong you can be in saying {"using" all of your CPU is a good thing} especially in a multi-user, shared memory environment such as an active Oracle instance. You see, Don, although "using" all of your CPU may be desirable if you don't waste any of it, in a multi-user system you can waste a lot of CPU very easily - even when nobody goes off the run queue.

Secondly: you love quoting Metalink and dredging up any Oracle documents, no matter how old, that might offer the slightest hint that you are right about one of your assertions; you love quoting Oracle marketing material as "proof" that one of your ideas must be good because Oracle mentions some planned feature that you can claim mimics your idea.

So why is it so hard to notice that Oracle's latest aid to performance automation, the ADDM report, makes comments like the following:

FINDING 1: 100% impact (1585 seconds)

-------------------------------------

Host CPU was a bottleneck and the instance was consuming 52% of the host CPU.

All wait times will be inflated by wait for CPU.

ADDITIONAL INFORMATION: Host CPU consumption was 88%.

CPU runqueue statistics are not available from the host's OS.

This disables ADDM's ability to estimate the impact of this finding.The CPU is running at only 88%, and ADDM warns you about it being a possible threat !

So much for 100% being normal or desirable or optimal.

Jonathan Lewis

http://jonathanlewis.wordpress.com

http://www.jlcomp.demon.co.uk