<page xmlns="http://projectmallard.org/1.0/" type="guide" style="task" id="harmful" xml:lang="sl">

    <info>

     <link type="guide" xref="index#harm"/>

    </info>

    <title>Disk Seeks Considered Harmful</title>

        Disk seeks are one of the most expensive operations you can possibly perform. You might not know this from looking at how many of them we perform, but trust me, they are. Consequently, please refrain from the following suboptimal behavior:

    <list type="unordered">

        <item>

                Placing lots of small files all over the disk.

        </item>

        <item>

                Opening, stating, and reading lots of files all over the disk

        </item>

        <item>

                Doing the above on files that are laid out at different times, so as to ensure that they are fragmented and cause even more seeking.

        </item>

        <item>

                Doing the above on files that are in different directories, so as to ensure that they are in different cylinder groups and cause even more seeking.

        </item>

        <item>

                Repeatedly doing the above when it only needs to be done once.

        </item>

    </list>

        Ways in which you can optimize your code to be seek-friendly:

    <list type="unordered">

        <item>

                Consolidate data into a single file.

        </item>

        <item>

                Keep data together in the same directory.

        </item>

        <item>

                Cache data so as to not need to reread constantly.

        </item>

        <item>

                Share data so as not to have to reread it from disk when each application loads.

        </item>

        <item>

                Consider caching all of the data in a single binary file that is properly aligned and can be mmaped.

        </item>

    </list>

        The trouble with disk seeks are compounded for reads, which is unfortunately what we are doing.  Remember, reads are generally synchronous while writes are asynchronous.  This only compounds the problem, serializing each read, and contributing to program latency.

</page>