On Fri, Mar 02, 2012 at 03:16:12PM +0100, Jacek Luczak wrote: > 2012/3/2 Chris Mason <chris.mason@xxxxxxxxxx>: > > On Fri, Mar 02, 2012 at 11:05:56AM +0100, Jacek Luczak wrote: > >> > >> I've took both on tests. The subject is acp and spd_readdir used with > >> tar, all on ext4: > >> 1) acp: http://91.234.146.107/~difrost/seekwatcher/acp_ext4.png > >> 2) spd_readdir: http://91.234.146.107/~difrost/seekwatcher/tar_ext4_readir.png > >> 3) both: http://91.234.146.107/~difrost/seekwatcher/acp_vs_spd_ext4.png > >> > >> The acp looks much better than spd_readdir but directory copy with > >> spd_readdir decreased to 52m 39sec (30 min less). > > > > Do you have stats on how big these files are, and how fragmented they > > are? For acp and spd to give us this, I think something has gone wrong > > at writeback time (creating individual fragmented files). > > How big? Which files? All the files you're reading ;) filefrag will tell you how many extents each file has, any file with more than one extent is interesting. (The ext4 crowd may have better suggestions on measuring fragmentation). Since you mention this is a compile farm, I'm guessing there are a bunch of .o files created by parallel builds. There are a lot of chances for delalloc and the kernel writeback code to do the wrong thing here. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
