New Alt.Binz versions > Closed requests

Pause With Automatic Resume

(1/3) > >>

rweldin:
Historically I've set my temporary download folder to a RAM disk, but recently ran into some issues after upgrading my internet. My connection is now so fast that my downloads fill up the RAM disk before the files can be decoded and deleted which causes the application to hit the pause download threshold hence pausing all downloads. It would be nice if the application resumed downloads as the temp files are decoded and deleted freeing up space for additional temp file downloads on the RAM disk. For now I've moved my temp file directory to a hard disk location which works OK, but my download speed dropped probably because of disk thrashing and all of the writes that are being done on the spinning drive.

Thanks for your consideration.

Rdl:
Done, but I didn't test it.

Please, when you try new version, test it and report results here.

rweldin:
Thank you for considering this and making a change. I wasn't able to get this change to work as the download would not resume after space was freed up when the temporary files were decoded and deleted.

Below are some reference times it takes to download and decode a test NZB. For the RAMDISK download I manually unpaused the download after enough temporary files were decoded and deleted to free up space for additional temp space for downloads.

Download to drive that contains the temp folder and download folder: 3:31
Download folder is the same as the drive above, but the temp folder is set to a RAMDISK: 1:48

If you have any questions please let me know.

Rdl:
Whatever was downloaded was it split into parts or 1 big file?
Cause logic is this: if write failed (not enough space) that file part is deleted, returned to not downloaded state, download paused and part size recorded. After every file decode, free space is checked and if larger then recorded part size then download is unpaused.

rweldin:
The test was done with a NZB that contained numerous rar parts split up into ~100MB files. Many 100 MB files were downloaded, but were not able to be decoded before the pause download threshold was met which paused the application. While the application paused decoding continued which eventually decoded all of the downloaded files and freed the space on the temp folder drive when the rar parts were moved to the download folder; the application never resumed even after the free space on the temp drive was more than 10x the pause threshold.

The pause download settings reference the destination drive. Is there any distinction in the pause logic between the temp folder drive and where the file is being downloaded to? In my case the application pauses when the RAMDISK is filled up with temporary files so the destination drive is actually the temp folder drive and not where the file is being downloaded to?

If you need any other information let me know. Thanks!

Navigation

[0] Message Index

[#] Next page