G
gus
Guest
What's a "bad" amount of fragmentation? Depends. When a row is fragmented, that means that the row (almost always) occupies more than one data block. This results in additional disk I/O and additional database buffer pool accesses which in turn affects performance. If all the rows in a table are in two fragments, this is probably bad. But if it is a table that doesn't get read very often, maybe it doesn't matter. So you have to consider the activity on the fragmented table in comparison to the overall workload. protop can show you that.
Continue reading...
Continue reading...