Parallel execution strategy

From: <>
Date: Mon, 17 Mar 2008 03:14:02 -0700 (PDT)
Message-ID: <>

Hi all,

A customer of mine is facing performance problems caused by bad single physical read rates. I'm working on the root cause. In the meanwhile I'm going to implement parallel execution since all resources on these servers are underused and there are just a few concurrent users all day long. With parallel execution enabled, the physical read rate for most queries with lots of gets is dramatically increased.

Any advice regarding the strategy to get the best results? Forcing parallel query/dml/ddl at the session level is no option (I've tried this out on a test plateform with very bad results such as application errors and, as expected, very long execution times for queries not benefiting from parallel execution.)
I'm currently identifying every queries with a bad read rate and a long execution time and I'm implementing parallel execution on the underlying objects (by testing each query on a test plateform). But this is somewhat time-consuming. ;-)

Jerome Received on Mon Mar 17 2008 - 05:14:02 CDT

Original text of this message