On Fri, 2009-02-20 at 11:01 -0500, Josef Bacik wrote: > On Fri, Feb 20, 2009 at 04:56:55PM +0530, srimugunthan dhandapani wrote: > > hi all, > > I would like to know what are the ssd specific optimisations in btrfs . > > I read from the archives that > > > > "mount -o ssd option, which clusters file data writes together regardless of > > the directory the files belong to. There are a number of other performance > > tweaks for SSD, aimed at clustering metadata and data writes to better take > > advantage of the hardware" > > Also I read that there are some allocator changes specific to ssd. I > > would like to know what these changes are. > > > > I tried to see the v 0.17 code to understand what ssd specific changes are. > > I saw that the SSD option was used in two places in function > > find_free_extent and in function btrfs_defrag_leaves. > > I couldn't gather much information from the code. > > So can somebody help me understand the optimisations and changes in btrfs. > > are any documentation or reading material available? > > Thanks in advance for helping, > > So really the only thing that changes with SSD is that we keep track of the last > place we allocated for data, and start looking from there again. Since there is > no seek penalty we can just be dumb in the allocator and use up space > sequentially regardless of the file instead of trying to group allocations for > the file/dir. Thanks, We already do this with metadata, but the ssd mode makes the metadata cluster that we try to allocate larger now. This change was made based on benchmarks with an SSD that is bad at random writes, and it made a significant difference for metadata writes. The short answer is that in ssd mode we don't try to avoid random reads. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
