On Thu, Aug 11, 2011 at 03:05:55PM -0600, Andreas Dilger wrote: > > That said, "orlov" is also mostly meaningless with flex_bg as well, since > there is very little real benefit/affinity from inodes being "close" to > their data blocks. We gain far more benefit from keeping the inodes > together than spreading them out and keeping them close to the data blocks. I'm going to be applying the patch remove the oldalloc allocator, but just for the record --- Orlov *does* matter (which is why it's a good thing the default allocator also uses an Orlov-like approach that's flex_bg aware). In fact, we saw significant latency drops that grew over time as more and more blocks got allocated. I traced it back to using bigalloc, which increased the average distance between the inode tables and the data blocks. So as you use larger bigalloc cluster sizes, which increases the block group size, it's a good idea to decrease the flex_bg size. Which is another way of saying that Orlov matters. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
