My knee jerk to investigating the use of multiple block sizes is to see if it would benefit LOB storage for third party app. In other words, would the LOBs benefit from having a 16k or 32k blocksize? Unfortunately, I have zero documentation about what the LOBs are and why in the world is the vendor putting certain non-LOB tables and indexes in the LOB tablespace. Of course I haven't gotten that far yet, but when I do, I'll let you know. Unless someone else here would like to chime in... :) GL! Rich ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of LS Cheng Sent: Tuesday, December 19, 2006 8:23 AM To: VIVEK_SHARMA@xxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Use of Multiple BLOCK Sizes ? I think the best practice is multi block size tablespaces are invented so you can transport them and not for performance reasons On 12/19/06, VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx> wrote: Folks Does use of Multiple BLOCK sizes (for different Tablespaces) help in Performance of a Hybrid Application? Any best practices, Links, Docs? Thanks indeed