Re: Several CPUs and the parallel option

Hi Richard,

Indeed it would be quicker. Having the tables partitioned and suitably I/O spread to limit the amount of time waiting on I/O would mean faster ops. Stuff in the end is queued to use the CPU(s).

I would still check first to see what the database is waiting on before going thru the process of changing the table/tablespace/datafile structure to handle parallel query. It simply takes away any ammo people use to blame for bad performance.

Parallel query is a great thing to use to improve performance, but it shouldn't be seen as a placebo for poor code/design/maintenance etc

Have Fun

--
An Oracle DBAs undocumented init.ora parameters


_OVERCOME_POOR_DESIGN = TRUE

_DISABLE_BAD_PERFORMANCE = TRUE


An Oracle DBAs undocumented init.ora parameters


_OVERCOME_POOR_DESIGN = TRUE

_DISABLE_BAD_PERFORMANCE = TRUE


Posted via dBforums
http://dbforums.com