Re: 64k or 128k stripe - 8k block 8 multiblock read?

Thanks Nuno. One site was suggesting to set it at 16k!! That would mean that one logical I/O of 64k on a FTS would generate 4 physical I/Os (assuming the stripe size per disk was 16k and there were 4 disks in the stripe set). His reasoning was that this would balance the I/O evenly over all 4 disks in the set. That made absolutely no sense to me at all because then you'd have to wait for all 4 physical I/Os to complete. Wouldn't that be slower?!

Domenic.

"Noons" <wizofoz2k_at_yahoo.com.au> wrote in message news:<3f6add0d$3$13416$afc38c87_at_news.optusnet.com.au>...
> "Domenic G." <domenicg_at_hotmail.com> wrote in message news:c7e08a19.0309181631.14ab09a4_at_posting.google.com...
> > Quick question ...
> >
> > Assuming a db_block_size of 8k with a db_file_multiblock_read_count of
> > 8
> >
> > 8k x 8 = 64k
> >
> > Should I set my disk stripe size to 64k or 128k for the most efficient
> > I/O for FTS? The Oracle docs give contradictory advice.
>
>
> I'd say 64K, but 128 shouldn't make that much difference. Provided
> of course your tables ARE larger than 128K! :D
>
> If you're running Windoze, you could go up to 512K, IIRC. There was
> a thread a while ago about this. Some Unix version will stop at
> 512, others will let you go 1Mb. I think HP/UX.
>
> www.ixora.com.au has some stuff on this.
Received on Fri Sep 19 2003 - 08:44:50 CDT