fujin/rtorrent
1
0
Fork 0
mirror of https://github.com/rakshasa/rtorrent.git synced 2026-10-05 13:49:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Disk allocation section on Performance Tuning page

chros73
2016-08-23 20:49:51 +01:00
parent 53ae063478
commit 5ec363597f
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Performance-Tuning.md
+10 -2
@@ -184,9 +184,17 @@ Large `fd_set`'s cause a performance penalty as they must be cleared each time t
#### Disk allocation
`system.file.allocate` specifies whether to allocate disk space for a new torrent. Default is `0`. It's suggested to leave it off: it reduce disk usage when a torrent is added.
`system.file.allocate` specifies whether to allocate disk space for a new torrent. Default is `0`.
Opening a torrent causes files to be created and resized with `ftruncate` (`ftruncate` has problem on vfat filesystem, though.) This does not actually use disk space until data is written, despite what the file sizes are reported as. Use `du` without the flag `--apparent-size` to see the real disk usage.
Why would you care about this setting? Because "it’s beneficial in the as-less-fragmentation-as-possible sense".
When it's enabled (set to `1`):
- on a non-blocking file system that supports `fallocate` (like btrfs, ext4, ocfs2, xfs) that is used to resize files, hence there is no performance issue
- if `fallocate` isn't supported by a blocking file system and `--with-posix-fallocate` was used during compilation of `libtorrent` then that is used to resize files, it can be [slower](https://log.amitshah.net/2009/03/comparison-of-file-systems-and-speeding-up-applications/) then the above one
- on Mac OS X a different method is used
When it's disabled (set to `0`):
- opening a torrent causes files to be created and resized with `ftruncate` (`ftruncate` has problem on vfat filesystem, though.) This does not actually use disk space until data is written, despite what the file sizes are reported as. Use `du` without the flag `--apparent-size` to see the real disk usage.
#### Session save