RE: Oracle internal flaws? (sure there are some, but zero of the one's in the OP for this thread are valid)

From: "Mark W. Farnham" <mwf@xxxxxxxx>
To: <jslowik@xxxxxxxxx>, <Mark.Brady@xxxxxxxxxxxxxxxxx>
Date: Tue, 15 Mar 2011 11:27:52 -0400
I'm curious what you think ASM has to do with the OS file system. What are
the media components of your disk groups?

 

mwf

 

PS: You can deploy any architecture stupidly (or cleverly?) to use it to
worst advantage. Fortunately it is not rocket science to deploy Oracle well.
In fact deploying Oracle just using all the defaults does amazingly well. Of
course if you're on some project that has high performance requirements and
must scale excellently, you might want to hire expert advice. But just
having read the concepts manual would make you expert enough to debunk this
original poster.

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Joel Slowik
Sent: Tuesday, March 15, 2011 10:35 AM
To: Mark.Brady@xxxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle internal flaws?

 

This stuck out to me:

"Especially noteworthy, because it uses file system files (not raw
partitions), and the "caching" is outside, it relies heavily on (and is very
sensitive to) the file system cache that you have set up. likewise, Oracle
needs a massive amount of memory for these processes."

That's true if you are using ASM or the file system to manage data files.
When creating a database, you can specify to oracle to use raw partitions as
a storage mechanism.

 

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Brady, Mark
Sent: Tuesday, March 15, 2011 10:09 AM
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Oracle internal flaws?

 

I saw this answer today on StackOverflow. 

 

http://stackoverflow.com/questions/5307590/cpu-usage-of-oracle-installed-dat
abase-machine

 

 

 

Quote from PerformanceDBA, a notable Oracle basher.

 

"Oracle does not have a true server architecture (others have it). Rather
than performing classic server tasks, such as multi-threading, caching of
data pages, parallel processing (split a query across many devices) etc.
within itself, it uses the o/s to do all that. That means for each user
process (PL/SQL connection) there is one unix process; 1000 users means 1000
unix processes, all competing for the same resources.

Especially noteworthy, because it uses file system files (not raw
partitions), and the "caching" is outside, it relies heavily on (and is very
sensitive to) the file system cache that you have set up. likewise, Oracle
needs a massive amount of memory for these processes."

 

I'm not enough of an internals guy to accurately refute these declarations.
Can anyone help me understand which of these statements are true and whether
or not they are deficiencies?

>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for
the addressee.  If you are not the intended recipient, do not use the
information in this e-mail in any way, delete this e-mail and notify the
sender. CEG-IP1

Confidentiality Note: This electronic message transmission is intended only
for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. If you have received this transmission, but are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of the contents of this information is strictly
prohibited. If you have received this e-mail in error, please contact
Continuum Performance Systems at {203.245.5000} and delete and destroy the
original message and all copies.
RE: Oracle internal flaws? (sure there are some, but zero of the one's in the OP for this thread are valid)

Other related posts:
