Re: direct path read (temp) 31 blocks per event

From: Mark D Powell <>
Date: Tue, 4 Nov 2008 05:26:04 -0800 (PST)
Message-ID: <>

On Nov 4, 8:05 am, HansP <> wrote:
> Version
> Platform: Linux
> During a performance test I noticed the that 'direct path read temp'
> where done with 31 blocks and sometimes with 1 block per wait.
> The 'db file scattered read' 's where done with 128 blocks per wait
> (db_file_multiblock_read_count was not set explicitly)
> Does someone know why the strange number of 31 is chosen for the
> direct path reads (at least for temp).
> I think that normal direct path reads were als done with 31 blocks but
> I am not completely sure about that.
> BTW I looked in v$sesion_wait P3 is the block count.
> Any suggestions
> Regards Hans-Peter

What kind of memory management is in use? What is the database block size?

This is only a guess since I do not have an 11g system to test with, but I suspect that the size chosen may have something to do with the size of the available in memory sort area.

Depending on the memory management in use and the number of concurrent working connections you had or can create you might be able to run some tests and see if the number varies with load.

HTH -- Mark D Powell -- Received on Tue Nov 04 2008 - 07:26:04 CST

Original text of this message