It depends. I've worked in shops there 32k blocks have done wonders, but they are not right for everyone. Multiple blocksizes are used in ALL the Oracle10g TPC-C benchmarks because they allow far faster transaction execution with less I/O. These vendors spent hundreds of thousands of dollars to get the fastest performance and their choice of multiple blocksizes speaks for itself.Is the creation of this large non-standard block size tablespace a bad idea?
The current block size of this tablespace is 8K. I amYou are having the "single-block read" as your top event - why would you want even more rows fetched this way? Maybe you interpreted the event in a different way?
thinking of creating a tablespace with non-standard
block size of 16k or 32k so that more rows will
fetched single block reads and moving all segments
into this tablespace.