This shows you the differences between the selected revision and the current version of the page.
| — | documentation:storage_modes 2009/03/24 16:36 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Storage Modes ====== | ||
| + | |||
| + | =====Sparse===== | ||
| + | All pieces will be written to the place where they belong and sparse files will be used. This is the recommended, and default mode. | ||
| + | |||
| + | =====Allocate===== | ||
| + | Same as storage_mode_sparse except that files will be ftruncated on startup (SetEndOfFile() on windows). For filesystem that supports sparse files, this is in all practical aspects identical to sparse mode. For filesystems that don't, it will allocate the data for the files. The mac filesystem HFS+ doesn't support sparse files, it will allocate the files with zeroes. | ||
| + | |||
| + | =====Compact===== | ||
| + | The storage will grow as more pieces are downloaded, and pieces are rearranged to finally be in their correct places once the entire torrent has been downloaded. | ||
| + | |||
| + | There is more information about the different storage modes at [[http://www.rasterbar.com/products/libtorrent/manual.html#storage-allocation]] | ||