0
I have noticed when using the Transmission WebUI on my Debian server that when a download begins, Transmission downloads about 5MB, and then stalls for a few minutes before continuing. On closer inspection, I realised that during this stall time is 'grows' the download file in my downloads directory. Once this file reaches the size of the download, the transmission download continues where it left off.
I am just wondering why it does this? Why does it expand the file to full size when the download begins rather than expanding it during the download? I had thought it could be something relating to free space, but it surely uses du
or something to check for free space in the downloads directory before downloading begins.
Yes, but out of order piece downloading doesn't require pre-allocation, does it? There are torrent clients that allow you to turn off pre-allocation, and this does not mean they then start downloading sequentially. – Karan – 2013-02-23T15:10:40.260
As I mentioned, it is implementation dependent. The Transmission client writes each segment into its exact location in the file(s). I suppose this is done to simplify the tracking of the stuff and to avoid later reordering of segments. Also, it simplifies the restart of the transmission when you stop the client and start it again later (for example, you switched off your PC as it is to noisy to let you sleep :) – Serge – 2013-02-23T15:14:34.107
Ah ok, haven't used Transmission all that much. So it has no option to turn pre-allocation off? – Karan – 2013-02-23T15:18:04.560
Just checked with its man page - there is no such option. – Serge – 2013-02-23T15:21:49.877
Actually, I found when the option was added, and also how it can be disabled if required. There's even a "full" option as well apparently (default is "fast").
– Karan – 2013-02-23T15:25:07.020