In a heavy duty OLTP system with lots and lots of scattered reads all over the place - this might be bad as no one is going after the same blocks (eg: I read a row on a block and no one else ever needs that block - i cached lots of stuff no one is going to use and I may have bumped out some other data that we could have used). For every row you want, you might get N times as many rows pulled along.

O you will have the same amount of data cached (volume) but the granularity of the data will be N times larger. We do lots of stuff at the block level - you may notice more contention in this area. O you will have more people contending for the same block perhaps. Going from 2k with a 10% pctfree (default) to an Xk block with 10% free means we have perhaps more free space on each block to accomidate this (but we also have more rows per block so it might not matter all of the time). We leave the 'head' of the row on the original block (cannot change the rowid) and put the row itself on another block entirely. Row migration happens when we attempt to update a row but discover there is insufficient space on the block to do so. Row chaining happens when a row is too large to fit on one contigous block - this is much less likely in an Xk block then a 2k block. O you will have less row chaining and perhaps less row migrations.

If you have a block that is 4 times LARGER you will have less then 1/4 the block overhead after you change over. There is a fixed amount of overhead per block.

O the amount of block overhead in your database will decrease. Here are a couple of pros and cons (some of them will be both pros and cons - depends on your perspective).

GPU-Z 2.56.0 for iphone instal