[mafourti]

Hi

I'm downloading onto a shared folder mapped to a letter on windows using smb, but when the download start, it download a few mb and then freeze for some time (nothing is downloaded, 0 b/s), during the creation of the empty file.
I'm writing to a HDD.

The hard drive is plugged to a linux raspberry pi and formatted to ext4

This does not happen if I download onto a SSD locally.

Here is what happens using process monitor:
when the download start :
**External links are only visible to Support Staff**

After 1 minute, the download really start :
**External links are only visible to Support Staff**

the file is 8.897 Gb. I have setup to download using 2 chunks. I don't know why it really start downloading once it have pre allocated only the half (4gb) according to process monitor.

Setting to 1 chunk solve the problem, but the download speed is lower.

what can I do to improve that ?

[raztoki]

for memory last chunk is amended and grows in size as it downloads.

so chunks (c), filesize (f), preallocation (p),
p = (f / c) * ( c - 1)

you're better off not saving over network for download when lag events happen. save locally and move as a post event, you will still get lag on the post event, but it wont effect the download. I've experienced this myself on slow drives in the past usually within VM environments. Downloads end up timing out due to waiting for pre-allocation tasks to complete before the write task can commence. The larger the file, the worse the outcome. I've seen it time-out multiple times and even lock up systems, as it JD can move onto another download and pre-allocate again so you end up with multiple problems.

And maybe another workable solution is to not using more than 1 chunk is also a solution, as it just grows vs pre-allocates

[mafourti]

does it says that sparse file are not working on my network drive if it so slow to pre allocate ?