Re: Memory operations on Sun/Oracle M class servers vs T class servers
From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Tue, 16 Dec 2014 22:55:40 -0400
Message-ID: <CAMHX9JJQEbwDr6B14DfsUZsjhV1TFO74_egNoSwt9wf=f+=U4Q_at_mail.gmail.com>
And reading your original email all the way to the end - depending on the exec plan the FETCH part may be the easy part - EXEC for example needs to pin the cursor, put binds in place in memory, walks through the execution plan "initializes" various row sources that may mean memory allocation (but for SELECTs, the actual plan execution and row production starts in FETCH)... So, can't assume that EXEC is less memory intensive than a 4 logical IO-doing fetch that follows it.
Date: Tue, 16 Dec 2014 22:55:40 -0400
Message-ID: <CAMHX9JJQEbwDr6B14DfsUZsjhV1TFO74_egNoSwt9wf=f+=U4Q_at_mail.gmail.com>
And reading your original email all the way to the end - depending on the exec plan the FETCH part may be the easy part - EXEC for example needs to pin the cursor, put binds in place in memory, walks through the execution plan "initializes" various row sources that may mean memory allocation (but for SELECTs, the actual plan execution and row production starts in FETCH)... So, can't assume that EXEC is less memory intensive than a 4 logical IO-doing fetch that follows it.
Tanel
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Dec 17 2014 - 03:55:40 CET