Method R Discussion GroupMethod R helps developers, DBAs, and decision-makers optimize Oracle-based software in every phase of the software life cycle. |
|
Discuss Method R products, techniques, and events. Ask new questions or post your own responses. |
No.
You should use the Profiler to summarize each thread's trace file separately; that is, for the query coordinator and each child server process. The QC's trace file will have a big PX event in it representing a gap that the server processes will give you the detail for. The game is laying out the parallelization in your mind so that you can "see" where all of your time has gone. Here's an ASCII rendition of a sequence diagram to show what I mean: QC child1 child2 ------- ------- ------- - work - work - PX call - work - work - work - work - work - work - work Here, each column represents a separate trace file, and elapsed time flows from up to down. While the QC's PX call takes place, the two child sessions are really doing all the work. To "tune" the process represented by the picture here, you'd need to focus your attention upon the child2 trace file, because its performance dominates the height of the sequence diagram (4 units for child2 versus 3 units for the QC). Note that the 2 units of work for child1 are really irrelevant as long as its parallel sibling (child2) consumes 2 or more units of work. Hope this helps... |
Powered by FogBugz