You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
Expecting a double in parallelism to yield a two times performance improvement is a best-case scenario that is unlikely. So there are a number of reasons why parallelism can be limited:
* Processes that are split typically must have their results merged, which may force the creation of an additional process or, if the merge process already exists, it may take more time to complete.
In reality, with every additional parallel resource (for example, CPU core), a fraction of the power effectively becomes unavailable or lost. As mentioned, if a batch process is split, there may be the need to merge the results. The merge process is the direct result of the increased parallelism, and this constitutes a piece of perceived processing gain we effectively lose. It's true that overall we can reduce elapsed time, but the scalability effect is real, and it grows as the number of parallel streams increases.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|