C
ChUIMonster
Guest
Creating Storage Areas (extents are the individual files that make up a storage area) with finely tuned rows per block has very few benefits these days. Personally I still do it. 1) it's a habit 2) it's not that hard so long as you don't obsess over the decimal point and 3) I have certain tools that I sometimes run which use Monte Carlo sampling of RECIDs. They run a lot faster if there aren't a lot of missing recids 
If you are going to take the "one size fits all" approach then you should probably choose 128 or 256. Some people argue that 256 is pointless because nobody has records that small. I happen to know of some tables whose records are indeed that small. So I go with 256 when I am doing that. In my experience 8K blocks will give somewhat better read performance. Even on Windows. But it is not usually enough to argue about.
Continue reading...
If you are going to take the "one size fits all" approach then you should probably choose 128 or 256. Some people argue that 256 is pointless because nobody has records that small. I happen to know of some tables whose records are indeed that small. So I go with 256 when I am doing that. In my experience 8K blocks will give somewhat better read performance. Even on Windows. But it is not usually enough to argue about.Continue reading...