Tags: jesec/rtorrent
Tags
rTorrent 0.9.8, -jc Release 16 - allow to preallocate space for the whole torrent at once To enable, "system.file.allocate.set = 2". Currently, with system.file.allocate = 1, rTorrent preallocates space only after the file is opened for write. In many cases, it is preferable to preallocate space for the whole torrent at once, to reduce fragmentation of contents inside the torrent. It allows more efficient filesystem organization, where files that are likely to be read together are packed in contiguous area of the disk, improving the performance and I/O patterns of future read operations.
rTorrent 0.9.8, -jc Release 15 - "d.timestamp.last_active" is now updated when the user stops an active torrent manually. - when JSON RPC is used, rTorrent is able to acquire global lock later and release it earlier. Hopefully, this would allow less contention and better performance.
rTorrent 0.9.8, -jc Release 14
- Add "download.{active,inactive}" events
and "d.timestamp.last_active":
The function is fully event-based, and has a
well-defined and stable behavior.
"Activity" here means "last time any peer was
connected", consistent with @pyroscope's
definition of "d.timestamp.last_active" in
https://rtorrent-docs.readthedocs.io.
Some caveats: the date would only be recorded
when the last peer disconnects naturally. So if
the user manually stopped the torrent, or stop
the rTorrent when the torrent is still active,
the timestamp would not be recorded. This is
because when the torrent closes (or download
object destructs), pending events are destroyed
as well. Additionally, users have to check if
the torrent is currently active by themselves,
so rTorrent does not have to frequently write
current time to the session.
PreviousNext