On Mon, Sep 27, 2010 at 04:01:11PM -0700, Darrick J. Wong wrote: > > Other than those regressions, the jbd2 fsync coordination is about as fast as > sending the flush directly from ext4. Unfortunately, where there _are_ > regressions they seem rather large, which makes this approach (as implemented, > anyway) less attractive. Perhaps there is a better way to do it? Hmm, not much chatter for two weeks. Either I've confused everyone with the humongous spreadsheet, or ... something? I've performed some more extensive performance and safety testing with the fsync coordination patch. The results have been merged into the spreadsheet that I linked to in the last email, though in general the results have not really changed much at all. I see two trends happening here with regards to comparing the use of jbd2 to coordinate the flushes vs. measuring and coodinating flushes directly in ext4. The first is that for loads that most benefit from having any kind of fsync coordination (i.e. storage with slow flushes), the jbd2 approach provides the same or slightly better performance than the direct approach. However, for storage with fast flushes, the jbd2 approach seems to cause major slowdowns even compared to not changing any code at all. To me this would suggest that ext4 needs to coordinate the fsyncs directly, even at a higher code maintenance cost, because a huge performance regression isn't good. Other people in my group have been running their own performance comparisons between no-coordination, jbd2-coordination, and direct-coordination, and what I'm hearing is tha the direct-coordination mode is slightly faster than jbd2 coordination, though either are better than no coordination at all. Happily, I haven't seen an increase in fsck complaints in my poweroff testing. Given the nearness of the merge window, perhaps we ought to discuss this on Monday's ext4 call? In the meantime I'll clean up the fsync coordination patch so that it doesn't have so many debugging knobs and whistles. Thanks, --D -- 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
