On Tue, Nov 25, 2008 at 03:41:15PM -0700, Andreas Dilger wrote: > > Stupid question... if the goal is to not have the average commit time > > not react too strongly to sudden and vast changes to the commit time, > > would it be better to do this instead: > > > > > + journal->j_average_commit_time = (commit_time + > > > + journal->j_average_commit_time*3) / 4; > > Actually, yes. That is my fault, I'd suggested the original change to > Josef. BTW, I've added a patch to display the average commit time it does vary wildly, especially on a laptop hard drive. While the system is idle, and the occasional commits need to wait for the hard drive to wake up, leads to a average commit time of around 80-140ms. If the disk is just getting lightly tickled, such that it never has a chance to go to sleep, the average commit time can drop down to around 20-25ms. If the hard drive is really busy, then the average commit time can go up to 40-50ms. Increasing the weight as described below will slow down the move to these long-term averages, but at least for laptop or Green Star drives with power savings enabled, the average commit time does seem to vary in some non-inintuitive ways. Of course, if we are capping the max transaction time at 15ms, most of this will never be visible, but it would probably be interesting to test out this patch on a fast SSD or an expensive enterprise array to see whether are similar surprising variations in the average commit time. - 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
