Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[luquino]

Is it possible to know how much disk space will be occupied (when the download will ends)  from the files currently downloading?

[Stu Redman]

You mean total size of all downloads minus effective size of temp folder (considering sparse file effects) ?
No, there's no function for that at the moment afaik.

[luquino]

ok, and the absolute total amount of disk space required for the downolad, regardless the tmp files?

[Stu Redman]

Looks like even that info is not there at the moment. 

[lfroen]

ok, and the absolute total amount of disk space required for the downolad, regardless the tmp files?

Eeee - you mean size of your file?!

[Stu Redman]

He might be downloading more than one of them.

[luquino]

ok, and the absolute total amount of disk space required for the downolad, regardless the tmp files?

Eeee - you mean size of your file?!

No.
I'll try with an example.
I ' m searching 4 files with aMule:
  - Ubuntu live 9.04 iso image 700 MB
  - Ubuntu alternate 9.04 iso image 698 MB
  - amule 2.2.4 tarball  4.5 MB
  - Debian Lenny iso image  136 MB
If I start to download these files I need 1538.5 MB of free disk space. When I start the downloads the amount of the disk space required is the same of the sum of the sizes of the files, during DL the tmp files growth up and free space on disk decreases.

 It would be nice to have a function that gives a look to the total of the files downloading and report the total of the disk space required (the sum of the files sizes), than calculate the amount of the DL already done and compare the delta with the space available on the disk, keeping in mind that during DL probably aMule need some more space for the tmp file than the actual size of the file downloading.

sum of sizes + extra space required - total downloaded = free space required
disk space avalaiable  - disk space required =  disk space remainig   (if negative    )

EMule does that and I think is not very hard to do it.

[lfroen]

Sorry, but I hardly see a point in such calculation. In your example you need at least 1.5Gb. Plus "some" overhead (size of .met files + sparse files handling). In case you don't allow sparse files, the overhead equal to size of .met file which is few Kb, which is less that 1% of file size and comparable to cluster size on your disk.

[luquino]

ok lfroen, may be is not so important to insert the overhead in the calculation, that is not the point.
The point is to have an instant situation of the disk space, this is important.
In the example I mention about 1.5 GB of download, but in the normal use I have much more Gigas downloading  at the same time, and be sure I am totally legal.

[Stu Redman]

I think is not very hard to do it.

At first glance not. But if you have temp files and 4 categories residing on 3 different drives (mounted relatively to each other), some sparse-capable, some not, then things can get slippery quickly, and hard to present.

[luquino]

... if you have temp files and 4 categories residing on 3 different drives (mounted relatively to each other), some sparse-capable, some not, ...

I don't understand well what you mean, but it's  my fault not yours, I will look for document about this argument and I will study hard.

Anyway, the easiest solution: for each file downloading you know both the total size and downloaded size (this data are displayed in DL window), just sum those two data in all the files downloading and report the total of  "Global size" and "Downloaded size" , you could put the total "still to download" as well.
That could be enough and doesn't  concern the technical problem you were mentioning.

[luquino]

no way?