RE: I/O and db_file_multiblock_read_count
- From: Kevin Lidh <kevin.lidh@xxxxxxxxx>
- To: Kevin Closson <kevinc@xxxxxxxxxxxxx>
- Date: Mon, 11 Dec 2006 07:38:57 -0700
I apologize for the tardiness of my response. This is the result of
timing the dd. It seems to indicate the same thing as the scattered
read test. Or am I reading that wrong?
(8k * 16)
Unix> time dd if=/ora/data/bordcdw/users/users01.dbf of=/dev/null
bs=131072
1290+1 records in
1290+1 records out
real 1.4
user 0.0
sys 0.5
(8k * 128)
Unix> time dd if=/ora/data/bordcdw/users/users01.dbf of=/dev/null
bs=1048576
161+1 records in
161+1 records out
real 4.0
user 0.0
sys 0.0
On Fri, 2006-12-08 at 15:48 -0800, Kevin Closson wrote:
> do the "same" thing using dd. Whatever your db_block_size is, plug it
> in as follows:
>
> $ time dd if=<datafile_for_the tablespace> of=-/dev/null
> bs=<block_size_in_bytes*16>
>
> then re-run:
> $ time dd if=<datafile_for_the tablespace> of=-/dev/null
> bs=<block_size_in_bytes*128>
>
> please let me know what you find
>
>
>
>
> ______________________________________________________________
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Lidh
> Sent: Friday, December 08, 2006 12:46 PM
> To: oracle-l
> Subject: I/O and db_file_multiblock_read_count
>
>
>
> I was reading an article about the appropriate setting for
> db_file_multiblock_read_count. I'm on a HP-UX 11.11 64-bit
> system with Oracle 9.2.0.7.0. The original value was 16 and I
> bounced the database and ran a million record full-scan test
> (10046 trace) and then set the value to 128 (max value) and
> re-ran the
--
http://www.freelists.org/webpage/oracle-l
- Follow-Ups:
- RE: I/O and db_file_multiblock_read_count
- From: Kevin Closson
- RE: I/O and db_file_multiblock_read_count
- From: Mark W. Farnham
- References:
- RE: I/O and db_file_multiblock_read_count
- From: Kevin Closson
Other related posts:
- » I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- RE: I/O and db_file_multiblock_read_count
- From: Kevin Closson
- RE: I/O and db_file_multiblock_read_count
- From: Mark W. Farnham
- RE: I/O and db_file_multiblock_read_count
- From: Kevin Closson