G
gus
Guest
> On May 4, 2016, at 3:02 AM, Grant Holman wrote: > > I've run proutil tabanalys to get the avg row size and then used this to split the tables into 256,128,64,32,8,4,2,1 RPB. this is not necessary. versions 10.1b ? and later have 64-bit rowid's (which you should enable if they are not so). this means theat you do not have to ever worry about running out of rowid's. The roughly 2.1 billion rowid (and record fragment) limit is gone. you do not have to be sure the maximum-rows-per-block is set low to avoid wasting rowids. forget about that. you only have to be sure that the maximum rows per block is set high enough that you don't waste too much space. for example: with maximum-rows-per-block set to 64, an 8k block with 64 records has room for about 6600 bytes of data. if your records average 50 bytes long (not common), then 64 records adds up to only 3200 bytes. so about half the block would be wasted (though it could be partly used if the rows in it expand during updates).
Continue reading...
Continue reading...